Skip to content

chore: adjust package engines versions #6725

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

Merged
merged 2 commits into from
Apr 8, 2025
Merged

Conversation

susnux
Copy link
Contributor

@susnux susnux commented Apr 5, 2025

☑️ Resolves

This package does not even target Node.JS so we could even drop the node dependency for `engines.
But lets at least allow the current LTS version (22) along side with LTS 20.

🏁 Checklist

  • ⛑️ Tests are included or are not applicable
  • 📘 Component documentation has been extended, updated or is not applicable
  • 2️⃣ Backport bugfixes to stable8 for maintained Vue 2 version.

This package does not even target Node.JS so we could even drop the
`node` dependency for `engines.
But lets at least allow the current LTS version (22) along side with LTS
20.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux susnux added the 3. to review Waiting for reviews label Apr 5, 2025
@susnux susnux added this to the 9.0.0 milestone Apr 5, 2025
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>

- name: Set up npm ${{ steps.package-engines-versions.outputs.npmVersion }}
run: npm i -g npm@"${{ steps.package-engines-versions.outputs.npmVersion }}"
node-version-file: package.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it doesn't support devEngines yet, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So no but works as long as devEngines are in the upper bound of the engines.
IMHO browser libraries like this do not even need any engine as they only target the browser not Node (in contrast to e.g. vite-config which targets Node).

Comment on lines +163 to +176
"node": "^20.11.0 || ^22",
"npm": "^10 || ^11"
},
"devEngines": {
"packageManager": {
"name": "npm",
"version": "^10",
"onFail": "error"
},
"runtime": {
"name": "node",
"version": "^22",
"onFail": "error"
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recall having a script to update all libs/apps

@skjnldsv skjnldsv merged commit 24ddc76 into main Apr 8, 2025
24 checks passed
@skjnldsv skjnldsv deleted the chore/package-engines branch April 8, 2025 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants