npm run publish succeeds but GitHub Pages does not render site
dldereklee opened this issue ยท 1 comments
Hi there,
I just configured my site and tested it locally using the npm run local command. Everything is working fine until I tried to deploy to GitHub pages using the npm run publish
Here is the output in the Terminal
Switched to branch 'chalk'
Your branch is up to date with 'origin/chalk'.
yarn install v1.7.0
info No lockfile found.
[1/4] ๐ Resolving packages...
warning npm > npm-registry-fetch@1.1.1: this version has a breaking change. use 1.1.0 or upgrade to latest
warning npm > npm-registry-fetch > make-fetch-happen > socks-proxy-agent > socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introducedin 2.1.0
[2/4] ๐ Fetching packages...
[3/4] ๐ Linking dependencies...
[4/4] ๐ Building fresh packages...
success Saved lockfile.
โจ Done in 5.07s.
Deployed Successfully!
But when I go to the deployed page it does not render like it is suppose to.
When I run npm run local it looks like this:
Not sure what I am doing wrong since there doesn't seem to be any errors. If it helps, here are the files that were generated for the gh-pages branch using npm run publish
Looks like the render-problem can be solved with setting baseurl
in config.yml
Also, if you are developing a project site, you must set the baseurl in _config.yml to the name of your repository.
check _config.yml
, and set baseurl: /your-repository-name
, then try deploy again