javascriptnodejs/node-addon-api #1339Not a task: already works

Add engines limitation into package.json?

envgap__nodejs__node-addon-api-1339

Original GitHub issue ↗Dated source checkout ↗Opened 2023-06-16

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 717a61931d7c14d12d59c763404256a5b07c72ce
Manifest: package.json
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

nodejs/node-addon-api #1339 · read the original issue

I just saw 7.0.0 and a changelog note about dropping Node.js 14 and 19 support ... I would have expected that this is also refelected in the package.json but there is no info at all.



Would it not make sense for less issues on developer and user side to have that in the package.json too?

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]