@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.
@julian that's what I thought but it's only installing v0.3.0. I was upgrading NodeBB from v0.8.x to v0.9.x and I ran into this issue. After running
./nodebb upgrade NodeBB won't start with warning about
npm i nodebb-theme-lavender but it keeps installing v0.3.0.
@pichalite Not sure if it's some npm cache issue... does this still happen on latest master? It should install 3.0.2 of lavender
@julian will verify and let you know
in my case, it is 3.0.2 that is pulled but ./nodebb doesn't seem to see that
@julian no issue setting up and starting NodeBB using latest master
Still get this on:
Author: Julian Lam [email protected]
Date: Sat Nov 28 21:40:20 2015 -0500
Using v0.9.x branch
[outdated] nodebb-theme-lavender installed v3.0.0, package.json requires 3.0.1
3/12 07:44  - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
3/12 07:44  - warn: ./nodebb upgrade
[cluster] Child Process (3875) has exited (code: 0, signal: null)
Workaround: npm i [email protected] <-- this works for me too
After upgrading from v0.9.0 to 0.9.1 the packages 'redis' and 'connect-redis' where not found.
I had to re-install them manually
Running './nodebb upgrade' always produced the same problem again
@wellenreiter I had to reinstall npm before I could run nodebb upgrade after running a pull
@wellenreiter Now that's weird... no reason why those packages should be deleted from
node_modules/ unless you're emptying the directory yourself every time you upgrade.
Even running ./nodebb upgrade on a working 0.9.1 installation produces the problem
It happened on my sandbox as well as on the production system.
Well, the upgrade is done, and there is no reason for me to worry about it. I just wanted to mention it, in case it's others had the same problem and to enable the developers to investigate, if needed