Signalk v2.14.0 requires node =>20? #181
Unanswered
bradharley
asked this question in
Q&A
Replies: 2 comments 1 reply
-
Yes, v20 is required and it has been that way for some time. (Although it did mostly work under v18) Can you please point out any documentation that says v18? It must have been missed. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I was going on step 4 which still had 18.x.
https://demo.signalk.org/documentation/Installation/Raspberry_Pi.html
...
3. Install NodeJS 20 and npm.
Follow instructions for Ubuntu and Debian based distributions like Raspberry Pi OS at NodeSource Distributions.
4. Ensure that we're using the latest version of npm.
sudo npm install -g ***@***.***
Copy
Use the following command to check the versions of NodeJS and npm installed.
node -v && npm -v
Copy
Ensure the reported versions are equal to or greater than v18.15.0, 9.5.0 respectively.
Step three obviously says to install v20.
QUESTION: Should I just install v22 which is current LTS?
Thanks as always,
Brad
…On Fri, Jun 13, 2025, at 11:52 AM, Scott Bender wrote:
Yes, v20 is required and it has been that way for some time. (Although it did mostly work under v18)
Can you please point out any documentation that says v18? It must have been missed.
—
Reply to this email directly, view it on GitHub <#181 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEHFXEYROHPCMW3WUYXYMT3DMFXTAVCNFSM6AAAAAB7IVCTLWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNBWGM4DKNY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
upgraded via the webui from 2.13.5 to 2.14.0 and it fails after restart. I get the following:
bharley@tweety:~$ sudo systemctl start signalk.service
-->
signalk-server[6623]: The installed version of node (v18.20.8) is older than the minimum required version (>=20). See https://github.com/SignalK/signalk-server/wiki/Installing-and-Updating-Node.js for more information how to upgrade.
Here are my node versions.
bharley@tweety:~$ node -v && npm -v
v18.20.8
10.8.2
Based on the docs, I reinstall from the command line.
bharley@tweety:~$ sudo npm install -g signalk-server
npm warn deprecated [email protected]: 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.
npm warn deprecated [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
added 1 package, removed 1 package, and changed 692 packages in 3m
122 packages are looking for funding
run
npm fund
for detailsThen it started fine with... sudo systemctl start signalk.service but still on 2.13.5...
Ran upgrade again via webui and get the following in the logs
2025-06-13T11:11:44.550146-06:00 tweety signalk-server[7947]: npm warn EBADENGINE package: '[email protected]',
2025-06-13T11:11:44.550213-06:00 tweety signalk-server[7947]: npm warn EBADENGINE required: { node: '>=20' },
2025-06-13T11:11:44.550266-06:00 tweety signalk-server[7947]: npm warn EBADENGINE current: { node: 'v18.20.8', npm: '10.8.2' }
Q:--So, I presume 20 or greater is required, but I can't find anything in the release notes denoting this, and the latest docs all reference v18. I don't mind upgrading, but what's the recommendation?
Beta Was this translation helpful? Give feedback.
All reactions