fatal: reference is not a tree: e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0

[Empty2k12]

Looks like someone force pushed

[stefanjudis]

Hello! 👋

Is this still an issue?

[cboillat]

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
npm ERR! fatal: reference is not a tree: e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0

I'm using node 9.3.0 and npm 5.6.0.

Any idea ?

[stefanjudis]

@cboillat Sorry for the late reply.

How far do you come in the process? Can you post a longer long?

[Empty2k12]

@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 master instead of e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0. This should be a matter of searching for e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0 in the code base and replacing it with master.

[cboillat]

@stefanjudis I retried the contenful guide command and this time everything went good for me. But this time the latest steps used yarn instead of npm.

[stefanjudis]

Glad to hear that. Sorry that I haven't had a detailed look yet. It's still on my todo list. :/

[Zenocolo]

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
2018-01-30T13_33_05_894Z-debug.log

[stefanjudis]

@Empty2k12

I looked in the codebase and couldn't find the hash.

@Zenocolo

I just ran the complete same setup and couldn't reproduce your issue. :(

Logs

``` ▶ node -v v9.4.0

▶ npm -v
5.6.0

~/Projects/cf-blog-in-5-minutes 🐧 🙈 master (╯°□°)╯
▶ npm-reset

fsevents@1.1.3 install /Users/stefanjudis/Projects/cf-blog-in-5-minutes/node_modules/fsevents
node install

[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

uglifyjs-webpack-plugin@0.4.6 postinstall /Users/stefanjudis/Projects/cf-blog-in-5-minutes/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
node lib/post_install.js

now@5.3.3 postinstall /Users/stefanjudis/Projects/cf-blog-in-5-minutes/node_modules/now
node postinstall.js

Downloading now for macOS [====================] 100%

nuxt@1.3.0 postinstall /Users/stefanjudis/Projects/cf-blog-in-5-minutes/node_modules/nuxt
opencollective postinstall || exit 0

                                 :=.
                                -=+=:   :-
                              .-=+++=: :++=.
                             .-+++++++=++++=.
                            .=+++++++****++++.
                           :=+++++++******++*+:
                          :=+++++++********++*+:
                         :=+++++++**********++*+-
                        -=+++++++*************+*+-.
                      .-=======+**************++++=.
                      .........::::::::::::::::::::.


                      Thanks for installing nuxt 🙏
             Please consider donating to our open collective
                    to help us maintain this package.

                        Number of contributors: 86
                          Number of backers: 66
                        Annual budget: US$ 14,843
                        Current balance: US$ 2,972

       👉  Donate: https://opencollective.com/nuxtjs/donate

npm notice created a lockfile as package-lock.json. You should commit this file.
added 1463 packages in 39.893s
npx: installed 27 in 2.557s

</details>

[aperezl]

delete package-lock.json file before install working for me.

[stefanjudis]

I pushed v1.1.1 with an updated package-lock.json and ran and manual setup and also a setup via contentful guide.

Can you let me know if the problem persists? :)

[peterwillcn]

uses: actions/checkout@v2 fixed

[Kashif-Azeem-Ahmed]

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
npm ERR! fatal: reference is not a tree: e9a9c62ce02115f7a4d7f197ba43362dcf0ea3d0

I'm using node 9.3.0 and npm 5.6.0.

Any idea ?

no idea