@julian said:
Muito Obrigado!
ahhahahahah 🙂 de nada!
NodeBB v1.13.2 released!
-
Hello everyone,
We've released a minor patch v1.13.2. Check out our GitHub page for the fixes: https://github.com/NodeBB/NodeBB/milestone/89?closed=1
Cheers!
-
The plugin nodebb-plugin-custom-pages Does not match this version! Please disable it before updating!
-
Milestone include https://github.com/NodeBB/NodeBB/issues/8137 ?
-
@Normando Yes
-
@shmuel4 What error do you see? Custom pages should be working with this patch version...
-
@Normando
I did not check log.
After updating the nodeBB did not go up without disabling the extension. -
Hi i'm upgrade error with sharp
info sharp Using cached /home/theworms/.npm/_libvips/libvips-8.9.0-linux-x64.tar.gz prebuild-install WARN install No prebuilt binaries found (target=8.17.0 runtime=node arch=x64 libc= platform=linux) make : on entre dans le répertoire « /srv/nodebb/node_modules/sharp/build » TOUCH Release/obj.target/libvips-cpp.stamp CXX(target) Release/obj.target/sharp/src/common.o make: g++ : commande introuvable sharp.target.mk:127 : la recette pour la cible « Release/obj.target/sharp/src/common.o » a échouée make: *** [Release/obj.target/sharp/src/common.o] Erreur 127 make : on quitte le répertoire « /srv/nodebb/node_modules/sharp/build » gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Linux 4.4.0-173-generic gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /srv/nodebb/node_modules/sharp gyp ERR! node -v v8.17.0 gyp ERR! node-gyp -v v5.0.5 gyp ERR! not okEDIT :
Solve with install libvips-dev
apt install libvips-dev -
Thanks for replying with the fix, @The-Worms !
-
And for fix :
Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist` Browserslist: caniuse-lite is outdated. Please run next command `npm update caniuse-lite browserslist`manually upgrade caniuse-lite and browserslist :
npm install [email protected]and
npm install [email protected] -
@The-Worms are you sure we use those deps?
Could be a subdependency -
I Have this notification :
(node:19103) DeprecationWarning: The option `autoReconnect` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 (node:19103) DeprecationWarning: The option `reconnectTries` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 (node:19103) DeprecationWarning: The option `reconnectInterval` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 (node:19103) DeprecationWarning: The option `autoReconnect` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 (node:19103) DeprecationWarning: The option `reconnectTries` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 (node:19103) DeprecationWarning: The option `reconnectInterval` is incompatible with the unified topology, please read more by visiting http://bit.ly/2D8WfT6 -
@julian said in NodeBB v1.13.2 released!:
@The-Worms are you sure we use those deps?
Could be a subdependencyYes with nodebb-plugin-browsing-users
-
First of all, a new fan and really love the design principles of NodeBB!
I might be too new to comment and make suggestion, but since I encountered
I wonder is it an option for the team of NodeBB to consider locking the dependencies version or publish
package-lock.jsonfor a production version release? -
Is there a specific reason that letters on the default avatars got smaller in this version (1.13) compared to previous ones?
