Skip to content

Conversation

@Apollon77
Copy link
Contributor

Assumed from last Changelog the current version supports Node.js 16, 18, 20 and we should also not block 21+ for now, Right?

fixes #1339

Assumed from last Changelog the current version supports Node.js 16, 18, 20 and we should also not block 21+ for now, Right?
Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

@legendecas legendecas merged commit afa494e into nodejs:main Jul 3, 2023
@legendecas
Copy link
Member

Thank you!

@espipj
Copy link

espipj commented Jun 26, 2024

Why was this added in a minor release? This is a breaking change and should have been released in a major version
This breaks for example installing https://github.com/parcel-bundler/watcher on Node 10 to 16...

legendecas added a commit to legendecas/node-addon-api that referenced this pull request Jul 8, 2024
legendecas added a commit that referenced this pull request Jul 12, 2024
@legendecas
Copy link
Member

Why was this added in a minor release? This is a breaking change and should have been released in a major version This breaks for example installing https://github.com/parcel-bundler/watcher on Node 10 to 16...

Released a patch version v7.1.1 to remove the engine requirement. We will still put the constraint on v8.x since we don't test older Node.js versions. Disable engine-strict if a person really want to use it with untested versions.

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.

Add engines limitation into package.json?

5 participants