Update 2.14.4
our Server is 2.14.0 and we want update to 2.14.4. The update doesn
t work at the signalk frontend. i think it doesn
t work because the 2.14.0 user have already node v20.19.3 and and 2.14.4 works with node 18? is that correct? What is the correct way to install 2.14.4 Step by Step8 Replies
2.14.4 works with v18 , v20 and v22
so your issue is not related to node version
Please check the Server Log for errors when updating
LOG: Jun 28 16:08:05 stderr: npm error code ENOTEMPTY
Jun 28 16:08:05 stderr: npm error syscall rename npm error path /usr/lib/node_modules/signalk-server npm error dest /usr/lib/node_modules/.signalk-server-1toVL4zJ npm error errno -39 npm error ENOTEMPTY: directory not empty, rename '/usr/lib/node_modules/signalk-server' -> '/usr/lib/node_modules/.signalk-server-1toVL4zJ'
Jun 28 16:08:05 stderr: npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-28T14_07_13_644Z-debug-0.log
I've never found why this happenes sometimes...
run
sudo rm -rf /usr/lib/node_modules/.signalk-server-1toVL4zJ
would probably happen if you restarted the server while the update was still runningits one step more... but now the LOG says stderr: npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
Jun 28 16:12:03 stderr: npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
Jun 28 16:12:03 stderr: npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
Jun 28 16:12:03 stderr: npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
Jun 28 16:12:04 stderr: npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
Jun 28 16:12:05 stderr: npm warn deprecated fstream@1.0.12: This package is no longer supported.
that's ok
normal warnings
but the server is still 2.14.0
you restarted?
you are sure the update was done running when you restarted?
now after a second restart it works fine.... thank you so much!