Ugrade error on 1.7.x - package.json not found

[julian]

That's quite odd! Do you have a package.json file in your root folder?

[PitaJ]

Run npm i

[fais3000]

@suparomana said in Ugrade error on 1.7.x - package.json not found:

./nodebb upgrade

I performed exact same upgrade i.e 1.6.1 to 1.7.3. These steps worked for me.

./nodebb stop
git fetch
git reset --hard origin/v1.7.x
npm i
./nodebb upgrade

[suparomana]

Thank you, guys! npm i was the solution.

[TaLoche]

Hello Guys,

I ran smoothly updates from v1.4.2 to v1.6.1 but when trying to get to v1.7.x I seem to have lost my package.json file in my root folder.

I did change my config.json along the way to change the ip to the domain name in the "url" section to avoid the connexion being lost with my host (following this topic https://community.nodebb.org/topic/11324/error-listen-eaddrinuse-0-0-0-0-4800-looks-like-your-connection-to-nodebb-was-lost-please-wait-while-we-try-to-reconnect/9)

v1.6.1 works fine and I have this when I run a git status

# git status
# On branch v1.7.x
nothing to commit, working directory clean

but as soon as I try to run ./nodebb upgrade I get this

/root/nodebb/src/cli/index.js:29
                throw e;
                ^

TypeError: Cannot read property 'R_OK' of undefined
    at Object.<anonymous> (/root/nodebb/src/cli/index.js:11:64)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/root/nodebb/nodebb:5:1)
    at Module._compile (module.js:541:32)

I did try npm i but since I never get a package.json file I'm still stuck as soon as I try to run ./nodebb upgrade is there a way around this?
Thanks for any help!

[PitaJ]

What version of Node and npm are you using?

[TaLoche]

@pitaj Hi PitaJ, thanks for stopping by!
npm 3.9.3 and node v6.2.1

[PitaJ]

@taloche it appears that that error is happening because you're on an older version of Node 6. For security reasons and for compatibility with NodeBB, you should upgrade to either the latest Node v6 or a newer major version like Node 8

[TaLoche]

@pitaj thanks for the idea! I'll jump to Node 8.
I'll keep you posted if this works out. Thanks again.

[TaLoche]

@pitaj Thanks! With node v8.7.0 and npm v5.4.2, I was able to run ./nodebb upgrade and now I'm a proud member of the nodebb v1.7.4 club.