Fix package.json engines and required Node version #950
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.