Update, merge issue..

julian

@Danny-McWilliams Nope, that should only apply to bundled plugins (mentions, vanilla/lavender/persona theme, markdown, etc).

If you're getting more of those "cannot find module" errors, then perhaps your dependencies were not completely installed.

Please run npm install.

Danny McWilliams

Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

Tried to start nodebb, this was in log.

codejet

@julian i run ./nodebb upgrade after it looks successful npm i command ?

./nodebb upgrade

module.js:340
    throw err;
          ^
Error: Cannot find module 'ini'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/node_modules/npm/node_modules/config-chain/index.js:4:11)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

21/7 20:21 [25890] - error: Error: Cannot find module './build/Release/magic'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
Error: Cannot find module './build/Release/magic'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

module.js:340
    throw err;
    ^
Error: Cannot find module './build/Release/magic'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

codejet

npm i is your phriend

NodeBB Upgrade Complete!

Bri

@Danny-McWilliams said:

Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

Tried to start nodebb, this was in log.

Usually when I get issues like this, I have to do an npm cache clean and then an npm install or npm rebuild

codejet

for some reason my ./nodebb upgrade script after git pull missed a ton of modules

leksar

trying to update, but npm i shows me that

npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires async@'~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 string@'~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 nodebb-theme-vanilla@>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~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 ?

codejet

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

leksar

same result

codejet

@leksar try run ./nodebb upgrade
paste error from th@ ?

leksar

leksar@ubuntu:~/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!

codejet

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

leksar

@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.

julian

@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

leksar

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 nodebb-theme-vanilla@>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~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

julian

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!

leksar

leksar@ubuntu:~/nodebb$ sudo npm unl -g nodebb-theme-ifsta-ui
npm WARN uninstall not installed in /usr/local/lib/node_modules: "nodebb-theme-ifsta-ui"
leksar@ubuntu:~/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 nodebb-theme-vanilla@>=0.0.137
npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~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
leksar@ubuntu:~/nodebb$

julian

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.

drew

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

leksar

I think I get it