-
-
Notifications
You must be signed in to change notification settings - Fork 598
Closed
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and the Parse JS SDK.
Issue Description
According to the readme, parse follows the supported node versions:
Parse JS SDK is continuously tested with the most recent releases of Node.js to ensure compatibility.
We follow the Node.js Long Term Support plan and only
test against versions that are officially supported and have not reached their end-of-life date.
We should align the repository with the currently supported Node.js versions: https://github.com/nodejs/Release
Steps to reproduce
Install parse when using Node.js 20 or 21. Get an engine warning:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.21.0 <17 || >=18 <20' },
npm WARN EBADENGINE current: { node: 'v21.4.0', npm: '10.2.1' }
npm WARN EBADENGINE }
Actual Outcome
Expected Outcome
According to the readme, no warning should occur.
Environment
- Node:
v21.4.0
[email protected]
kharlamov-itra
Metadata
Metadata
Assignees
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-alphaReleased as alpha versionReleased as alpha versionstate:released-betaReleased as beta versionReleased as beta versiontype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature