Upgrading to Nodebb v1.5.1
-
FWIW @julian @baris @psychobunny upgrading to npm@5 and using the package-lockfile.json thats generated could make these kinds of issues go away.
-
@bri npm@5 has some development usability issues. Namely, npm link is broken as an npm i in the main directory will dedupe out of linked modules, breaking lots of things.
-
output of
npm i
> node scripts/install.js npm WARN prefer global [email protected] should be installed with -g > [email protected] postinstall /home/ljhardy/public_html/nodebb/nodebb/node_modules/jsonpath > node lib/aesprim.js > generated/aesprim-browser.js > [email protected] install /home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3 > node-pre-gyp install --fallback-to-build [sqlite3] Success: "/home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3/lib/binding/node-v46-linux-x64/node_sqlite3.node" already installed Pass --update-binary to reinstall or --build-from-source to recompile npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/nock/node_modules/changelog requires chalk@'^0.5.1' but will load npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/chalk, npm WARN unmet dependency which is version 1.1.3 npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/nock/node_modules/changelog requires semver@'^4.0.3' but will load npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/semver, npm WARN unmet dependency which is version 5.3.0 npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/nock/node_modules/changelog requires wordwrap@'^0.0.2' but will load npm WARN unmet dependency /home/ljhardy/public_html/nodebb/nodebb/node_modules/wordwrap, npm WARN unmet dependency which is version 0.0.3
output of
nodebb upgrade
1. Bringing base dependencies up to date... OK 2. Checking installed plugins for updates... OK 3. Updating NodeBB data store schema... /home/ljhardy/public_html/nodebb/nodebb/public/src/utils.js:37 invalidUnicodeChars: XRegExp('[^\\p{L}\\s\\d\\-_]', 'g'), ^ TypeError: XRegExp is not a function at /home/ljhardy/public_html/nodebb/nodebb/public/src/utils.js:37:24 at /home/ljhardy/public_html/nodebb/nodebb/public/src/utils.js:8:20 at Object.<anonymous> (/home/ljhardy/public_html/nodebb/nodebb/public/src/utils.js:27:2) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object.<anonymous> (/home/ljhardy/public_html/nodebb/nodebb/src/utils.js:3:18) Error: undefined
-
What the heck? Sqlite3?
-
@ljhardy said in Upgrading to Nodebb v1.5.1:
I'm using mongodb, why would sqllite be referenced?
Um, you tell me That was the output in your installer script!
output of npm i
node scripts/install.js
npm WARN prefer global [email protected] should be installed with -g
[email protected] postinstall /home/ljhardy/public_html/nodebb/nodebb/node_modules/jsonpath
node lib/aesprim.js > generated/aesprim-browser.js[email protected] install /home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3
node-pre-gyp install --fallback-to-build[sqlite3] Success: "/home/ljhardy/public_html/nodebb/nodebb/node_modules/sqlite3/lib/binding/node-v46-linux-x64/node_sqlite3.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile