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

Fix package.json engines and required Node version #950

Merged
merged 1 commit into from
Oct 13, 2024
Merged

Conversation

tagliala
Copy link
Contributor

Including "pnpm" in the engines field of your package.json for a library is generally not recommended, even if you use it for building the library. The engines field is typically used to specify runtime environments (such as Node.js versions) that are required to run the library, not the tools used to build or develop it. Most developers expect the engines field to list only the runtime requirements, not development tools like package managers.

Including "pnpm" in the engines field of your package.json for a library
is generally not recommended, even if you use it for building the
library. The engines field is typically used to specify runtime
environments (such as Node.js versions) that are required to run the
library, not the tools used to build or develop it. Most developers
expect the engines field to list only the runtime requirements, not
development tools like package managers.
@coveralls
Copy link

Coverage Status

coverage: 100.0%. remained the same
when pulling 3dd8a9f on chore/fix-engines
into 36e1b19 on main.

@tagliala tagliala merged commit 17730ad into main Oct 13, 2024
23 of 26 checks passed
@tagliala tagliala deleted the chore/fix-engines branch October 13, 2024 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants