Skip to content

fix: unnecessary strict node requirement in engines in package.json #2498

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 1 commit into from
Oct 11, 2024

Conversation

mrgrain
Copy link
Contributor

@mrgrain mrgrain commented Oct 11, 2024

Fixes #1329

We already use jsii to manage Node.js versions. No need to overzealously enforce via engines.

@mergify mergify bot merged commit e9bf09c into 10.x Oct 11, 2024
13 checks passed
@mergify mergify bot deleted the mrgrain/fix/no-engines-version branch October 11, 2024 17:25
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.

Surprisingly strict node requirement in engines in package.json
2 participants