-
Notifications
You must be signed in to change notification settings - Fork 50
fatal: reference is not a tree: e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0 #28
Comments
Hello! 👋 Is this still an issue? |
Hi, When I npm install or go through contenful guide, I always end up with : npm ERR! Command failed: /usr/local/bin/git checkout e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0 I'm using node 9.3.0 and npm 5.6.0. Any idea ? |
@cboillat Sorry for the late reply. How far do you come in the process? Can you post a longer long? |
@stefanjudis The problem is the installer referring to a git branch that does not exist anymore. Make sure to change the npm command line to refer to |
@stefanjudis I retried the |
Glad to hear that. Sorry that I haven't had a detailed look yet. It's still on my todo list. :/ |
Same issue here, just in case you will find time to go over your todo list, running node 9.4.0 and npm 5.6,0 on OSX... LOG Attached |
I looked in the codebase and couldn't find the hash. I just ran the complete same setup and couldn't reproduce your issue. :( Logs``` ▶ node -v v9.4.0▶ npm -v ~/Projects/cf-blog-in-5-minutes 🐧 🙈 master (╯°□°)╯
[fsevents] Success: "/Users/stefanjudis/Projects/cf-blog-in-5-minutes/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node" is installed via remote
npm notice created a lockfile as package-lock.json. You should commit this file.
|
delete package-lock.json file before install working for me. |
I pushed Can you let me know if the problem persists? :) |
uses: actions/checkout@v2 fixed |
no idea |
Looks like someone force pushed
The text was updated successfully, but these errors were encountered: