Issue Overview
Deploying React app to GitHub Pages no longer works after upgrading dependency version of gh-pages from 3.2.0 to 3.2.1.
Issue Details
After the upgrade, now I am getting the error below when I run the npm script npm run deploy (which runs gh-pages -d build):
... (omitted) ...
> gh-pages -d build
Invalid URL: http:[email protected]:<username>/<project name>.git
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! <project name>@1.0.0 deploy: `gh-pages -d build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the <project name>@1.0.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
where <username> is the actual Git username and <project name> is the actual Git project name.
Additional Information
I used the SSH URL in git clone, not the HTTPS one.
This is what git remote -v gives me:
origin [email protected]:<username>/<project name>.git (fetch)
origin [email protected]:<username>/<project name>.git (push)
where <username> is the actual Git username and <project name> is the actual Git project name.
Findings
By checking package-lock.json, I find that filenamify-url is upgraded from ^1.0.0 to ^2.1.1, which may be the cause to the issue.
Downgrading the version back to 3.2.0 (not ^3.2.0) in my package.json and regenerating package-lock.json works for me.
See commit #393 d49620e
Issue Overview
Deploying React app to GitHub Pages no longer works after upgrading dependency version of
gh-pagesfrom3.2.0to3.2.1.Issue Details
After the upgrade, now I am getting the error below when I run the npm script
npm run deploy(which runsgh-pages -d build):where
<username>is the actual Git username and<project name>is the actual Git project name.Additional Information
I used the SSH URL in
git clone, not the HTTPS one.This is what
git remote -vgives me:where
<username>is the actual Git username and<project name>is the actual Git project name.Findings
By checking
package-lock.json, I find thatfilenamify-urlis upgraded from^1.0.0to^2.1.1, which may be the cause to the issue.Downgrading the version back to
3.2.0(not^3.2.0) in mypackage.jsonand regeneratingpackage-lock.jsonworks for me.See commit #393 d49620e