Latest pull breaks NodeBB, packages are out-of-date?
-
Cant start nodebb after a fresh install!
[outdated] nodebb-theme-lavender installed v3.0.0, package.json requires 3.0.1
30/11 13:43 [7595] - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
30/11 13:43 [7595] - warn: ./nodebb upgradeI have tried ./nodebb upgrade but it does not work. Does 3.0.1 exist?
Tips on this?
I am at
commit d4abd87112b6090fc5337d71e1b53c015e52e057
Author: Julian Lam [email protected]
Date: Sat Nov 28 21:40:20 2015 -0500Confirmed, latest pull breaks Nodebb for 0.9.x
-
@Jenkler ran into this issue yesterday. Try running this and it should work.
npm i [email protected]
-
@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 aboutnodebb-theme-lavender
Tried
npm i nodebb-theme-lavender
but it keeps installing v0.3.0. -
@pichalite said:
npm i [email protected]
Actually for me it install 3.0.1 but it still complains:
[outdated] nodebb-theme-lavender installed v.3.0.0, package .json requires 3.0.1
As a result I am dead in the water with an upgraded db schema but can't run nodebb
-
Still get this on:
commit d4abd87112b6090fc5337d71e1b53c015e52e057
Author: Julian Lam [email protected]
Date: Sat Nov 28 21:40:20 2015 -0500Using v0.9.x branch
[outdated] nodebb-theme-lavender installed v3.0.0, package.json requires 3.0.1
3/12 07:44 [3875] - 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 [3875] - warn: ./nodebb upgrade
[cluster] Child Process (3875) has exited (code: 0, signal: null)
Workaround: npm i [email protected] <-- this works for me too
-
Different problem:
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 manuallyRunning './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