javascriptexpressjs/body-parser #540Not a task: already works

Missing `engines` Field Update for Node.js Version Support in v2.0.0

envgap__expressjs__body-parser-540

Original GitHub issue ↗Dated source checkout ↗Opened 2024-10-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: 966bc9dd141cae791d5634a46af58435327b3170
Manifest: package.json
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

expressjs/body-parser #540 · read the original issue

Hi `body-parser` maintainers,



I noticed in the changelog for the latest release (v2.0.0) that there is a breaking change which states:



> Node.js 18 is the minimum supported version.



However, it seems that the `package.json` `engines` field was not updated to reflect this change.



Would it be possible to update the `engines` field in `package.json` to explicitly specify the range of supported Node.js versions? This would greatly help in ensuring compatibility when upgrading to `body-parser` v2.0.0.



Thank you for all your hard work on this project!

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

[]