Repository navigation
chore: declare Node >= 22.19.0 in package.json engines - #119
Merged
Merged
Conversation
The runtime depends on @platformatic/dynamic-buffer, which is ESM-only and requires Node >= 22.19.0. Declaring the engines field lets npm warn users on unsupported Node versions instead of failing at install/runtime. The CI matrix already runs 22/24/26.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The runtime depends on
@platformatic/dynamic-buffer, which is ESM-only and requires Node >= 22.19.0. Declaring theenginesfield lets npm warn users on unsupported Node versions instead of failing at install/runtime.The CI matrix already runs Node 22, 24, and 26, so this only aligns the package metadata with the supported range.