Skip to content
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

feat!: add engines.node field and node.js version check #1197

Merged
merged 6 commits into from Oct 18, 2021
Merged

Conversation

@pi0
Copy link
Member

@pi0 pi0 commented Oct 18, 2021

πŸ”— Linked issue

Resolves #800

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

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.json engines field + a background check in nuxi cli for all commands.

image

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.
@netlify
Copy link

@netlify netlify bot commented Oct 18, 2021

βœ”οΈ Deploy Preview for nuxt3-docs canceled.

πŸ”¨ Explore the source changes: a6c4176

πŸ” Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/616dc0039ab6ae0008c803b8

@pi0 pi0 changed the title feat(pkg): add engines.node field feat!: add engines.node field and node.js version check Oct 18, 2021
@pi0 pi0 marked this pull request as ready for review Oct 18, 2021
@pi0 pi0 marked this pull request as draft Oct 18, 2021
@pi0 pi0 marked this pull request as ready for review 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"
Copy link
Contributor

@productdevbook productdevbook Oct 18, 2021

I think it seems more correct this way? I was using this. "node": ">=14.18.0 || >=16.11.0"

Copy link
Member Author

@pi0 pi0 Oct 18, 2021

Both equally work :) You can try with this playground using >= we also allow intermediate non-LTS versions like 15.x which are not recommand.

@pi0 pi0 merged commit d8d10fe into main Oct 18, 2021
11 checks passed
@pi0 pi0 deleted the feat/engines-node branch Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

3 participants