for some reason my ./nodebb upgrade script after git pull missed a ton of modules
trying to update, but npm i shows me that
npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires [email protected]'~0.2.9' but will load
npm WARN unmet dependency /home/leksar/nodebb/node_modules/async,
npm WARN unmet dependency which is version 0.9.2
npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires [email protected]'~1.8.0' but will load
npm WARN unmet dependency /home/leksar/nodebb/node_modules/string,
npm WARN unmet dependency which is version 3.3.0
npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.0.18
npm ERR! System Linux 3.16.0-43-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
npm ERR! cwd /home/leksar/nodebb
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/leksar/nodebb/npm-debug.log
npm ERR! not ok code 0
Tried to do npm unlink nodebb-plugin-spam-be-gone and npm unlink nodebb-theme-ifsta-ui, but the result is the same. Any ideas ?
try npm uninstall nodebb-theme-vanilla and then reinstall it again, it might install the version that satisfies the dependancy.
Save changes made to vanilla too if need be 
same result
@leksar try run ./nodebb upgrade
paste error from [email protected] ?
[email protected]:~/nodebb$ sudo ./nodebb upgrade
[sudo] password for leksar:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
1. Bringing base dependencies up to date
Error: The package [email protected] does not satisfy its siblings' peerDependencies requirements!
sounds like unlinking those plugins did nothing.
I'm out of idea's but that was why it was complaining, maybe uninstall them if they aren't vital
I dont use shoutbox or that other thingo
@Codejet said:
I dont use shoutbox or that other thingo
I'm not using them too, just tried for some time. The weird thing is that even uninstalling doesn't help. I would remove them manually, if there is a way.
@leksar Remove them from node_modules/ is the most manual way 
Whenever the peer dependency error comes up, I just purge every module it mentions, and then run npm i
ok, so i restored my forum from a backup
removed all unnecessary plugins by ACP (including spam-be-gone and ifsta-ui)
checked that there was no plugin foldes in node_modules/
restarted forum and checked it works well
then:
sudo git checkout v0.7.x
sudo git fetch
sudo git reset --hard origin/v0.7.x
sudo npm i
there was no more warnings, but the errors still exists
npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.0.18
npm ERR! System Linux 3.16.0-43-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
npm ERR! cwd /home/leksar/nodebb
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/leksar/nodebb/npm-debug.log
npm ERR! not ok code 0
looks like the "links" are stored somethere else
Hm. Perhaps some of the modules were installed globally.
$ npm unl -g nodebb-theme-ifsta-ui
$ npm i nodebb-theme-ifsta-ui # not globally this time!
[email protected]:~/nodebb$ sudo npm unl -g nodebb-theme-ifsta-ui
npm WARN uninstall not installed in /usr/local/lib/node_modules: "nodebb-theme-ifsta-ui"
[email protected]:~/nodebb$ sudo npm i nodebb-theme-ifsta-ui
npm http GET https://registry.npmjs.org/nodebb-theme-ifsta-ui
npm http 200 https://registry.npmjs.org/nodebb-theme-ifsta-ui
npm http GET https://registry.npmjs.org/nodebb-theme-ifsta-ui/-/nodebb-theme-ifsta-ui-0.1.3.tgz
npm http 200 https://registry.npmjs.org/nodebb-theme-ifsta-ui/-/nodebb-theme-ifsta-ui-0.1.3.tgz
npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants [email protected]>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants [email protected]~0.0.18
npm ERR! System Linux 3.16.0-43-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i" "nodebb-theme-ifsta-ui"
npm ERR! cwd /home/leksar/nodebb
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! code EPEERINVALID
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/leksar/nodebb/npm-debug.log
npm ERR! not ok code 0
[email protected]:~/nodebb$
No need to run npm commands as sudo. In fact, it's actively discouraged.
Delete your node_modules/ folder again, and then run npm i as the leksar user.
Providing you've not done anything insane like edit things inside node_modules directly, or added packages without saving them in your package.json then a quick fix for this stuff is to do:
./nodebb stop
rm -rf node_modules #to remove your entire node_modules folder to start again
npm install #to install all your stuff from scratch
./nodebb config #to setup your database driver install
(press enter a lot on the config to use the same options as you already had installed)
./nodebb start
./nodebb log
I think I get it
Ok, problem is solved. The reason is my stupidity.
What we see on logs as "nodebb-theme-ifsta-ui" is not what it seems.
Month or two ago i manually copied folder nodebb-theme-ifsta-ui, renamed it and changed some strings in package.json, so it appered in ACP as separate theme which I was working on lately. So, after the removal of the theme update goes smoothly.
Shame on me, thanks for your help and sorry for your time 
Now, all what i need is to learn how to add my own theme properly.
@leksar said:
Now, all what i need is to learn how to add my own theme properly.
In that case, in your new theme, go into package.json and remove the peerDependencies section altogether. It's not really needed.
Thanks @BDHarrington7 but that didn't work either.
I'll backup & reinstall from scratch, probably the right idea this time as i've a Wordpress install which isn't behaving properly either, so I can tackle a number of issues head-on.
Cheers guys.
