Unhandled rejection Error: Command failed: /usr/bin/git checkout [email protected]

[asmundsollihogda]

Hi! Thanks for great work. I have problems with installing NPM and think that it might be since updating macOS.

How can this bug be reproduced?

1. Install foundationpress
2. run npm install

What happened instead?

Unhandled rejection Error: Command failed: /usr/bin/git checkout [email protected]
error: pathspec '4.0' did not match any file(s) known to git.

at ChildProcess.exithandler (child_process.js:289:12)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:962:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)

• OS & version: macOS 10.14
• Node version (node -v) [Node v4+ is required] : v10.12.0
• FoundationPress version (see line 3 in package.json): 2.10.4
• Foundation version (found in node_modules/foundation-sites/package.json) :

[prahladmishra]

I am getting the same error, I am on windows.

[RonEarl]

I posted the same issue a little big ago.

Frustrating. I think it's an issue getting the correct version of Gulp checked out.

-Ron

[DeiCha]

I've already posted solution: #1312
FIX:
update package.json line 42
from "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0"

[RonEarl]

Hi DeiCha,

That did not work for me. I got the same error.

-Ron

[DeiCha]

Strange, maybe package-lock.json din't updated when you've changed your package.json file.

If I were you I should try:

• change package.json
• npm rm -rf node_modules (to delete packages if some of them installed)
• delete: package-lock.json
• try npm init and npm install again

When solving my problem I've tried:

• clean cache (npm cache clean --force).
• reinstall git completely

Hope something helps. When googling about this I came to branch conflict problems. But i don't think it's the case when you do clean install.

[asmundsollihogda]

Reinstalling git as a clean install and changing:
package.json line 42 from "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0"
...helped me solve this problem.

Thank you for your help! @DeiCha

[michalchovanak]

changing "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0" helped me, thank you!

[Pixelsmith]

I ran into the same wall that @RonEarl did. I'm a certified N00b, but the current version of the theme on Github comes with package-lock.json pre-installed, even though I'm not seeing it listed on the file list on Github.

If I make @DeiCha 's change on line 42 and delete the package-lock.json file then I can get NPM install to work, and the package-lock.json reappears after install.

I'm using git clone via Windows command line to install the theme, but I can't imagine why that'd auto-create the package-lock.json file.

[mrlescodes]

Thanks @DeiCha, changing "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0" worked for me too

[BakaloMykhailo]

Thanks @DeiCha, changing "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0" works

[LilyReile]

I believe what happened is that the gulpjs team deleted the branch 4.0 when they released that version as a package. @DeiCha 's fix targets that release instead of the git branch directly.

[neilwave]

• OS & version: macOS 10.14
• Node version (node -v) [Node v4+ is required] : v10.12.0

On Mac OS X El Capitan 10.11.6
I had the same issue using node version 10.x

I am not an expert, but when i get it right version 6.11.x is recommended as highest version:
https://github.com/olefredrik/FoundationPress#requirements

I downgraded node to 6.11.5

sudo npm cache clean -f
sudo npm install -g n
sudo n 6.11.5

changed package.json line 42: "gulp": "^4.0",

and it works (for me)

[riverus-dev]

Thanks @DeiCha changing "gulp": "gulpjs/gulp#4.0", to "gulp": "4.0" helped me, thank you!

[millturnK]

You shouldn't need to downgrade node. All I did was this and it amended my package and package-lock files appropriately:
npm install gulp@next --save

[zamson]

I had to run rm package-lock.json and then it worked.

[alexander-young]

The reference to gulpjs/gulp#4.0 wasn't in the package.json but it was still in the package-lock.json and had to delete it out of there and then re-install the packages.