feat!: add engines.node field and node.js version check
#1197
+46
β1
Conversation
|
|
engines.node fieldengines.node field and node.js version check
productdevbook
reviewed
Oct 18, 2021
| @@ -56,6 +56,6 @@ | |||
| }, | |||
| "packageManager": "yarn@3.0.2", | |||
| "engines": { | |||
| "node": "^14.18.10 || ^16.11.0" | |||
| "node": "^14.18.0 || ^16.11.0" | |||
I think it seems more correct this way? I was using this. "node": ">=14.18.0 || >=16.11.0"
Both equally work :) You can try with this playground using >= we also allow intermediate non-LTS versions like 15.x which are not recommand.
productdevbook
approved these changes
Oct 18, 2021
danielroe
approved these changes
Oct 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Resolves #800
Ensure using latest Node.js version (Currently
^14.18.0 || ^16.11.0) to avoid unwanted issues due to old node version usage. We will keep maintaining this constraint under non-major releases to require LTS version of node as minimum.Using
package.jsonengines field + a background check in nuxi cli for all commands.The text was updated successfully, but these errors were encountered: