-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ReadMe] Update NodeJS Version in Readme #292
Comments
The current suggestion was made based on the compatibility of |
The current version is 5.1.6 which can be found here: https://www.npmjs.com/package/sqlite3/v/5.1.6 The compatibility statement for NodeJS 11, 12, 13 and 14 has been removed. The only mention of specific NodeJS versions is the one below.
I have been running SquadJS with NodeJS v18.16.0 since I had to upgrade 2 months ago. I have a sqlite database configured and everything worked so far. |
Going by the info provided above about why the version is recommended: The NPM info for sqlitev5.1.6 below: Notes that Node-API v3 is supported. The Node-API version matrix below
Notes that v3 is supported by all releases >v10 I believe it is safe to remove that version specific readme warning and recommend the latest Node LTS be deployed until either node-api deprecates v3.0 from a future release or nodejs sqlite drops support for api v3 |
as of today, you can't run the project with node 14. some of the dependencies are requiring 16 or above |
Description of Issue
SquadJS's readme lists NodeJS v14 as a prerequisite, this information is problematic as NodeJS 14's End of Life is today so the inherit recommendation of Node v14 is problematic to end users.
I believe this should be updated to either not describe an explicit version or mention the current LTS release (currently node 18)
Errors or Screenshots of Issue
https://endoflife.date/nodejs
Squad Information
If potentially relevant, please provide regarding the state of the Squad server at the time of error, e.g. the current layer.
System Information
The text was updated successfully, but these errors were encountered: