Skip to content

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

Closed

Description

@Phillip9587

Hi finalhandler maintainers,

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

drop support for node <18

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 finalhandler v2.0.0.

Thank you for all your hard work on this project!

Activity

  1. added a commit that references this issue on Oct 16, 2024
    72fd482
  2. wesleytodd commented on Jan 16, 2025

    @wesleytodd
    Member

    Yeah we can do this. We decided to add it as a minor in a few other packages because it was missed in the initial release. While it is technically a breaking change, it's omission was an oversight and so aligns with the policy we have set.

  3. Phillip9587 commented on Jan 16, 2025

    @Phillip9587
    ContributorAuthor

    There already is PR #59 for this change.

  4. wesleytodd commented on Jan 16, 2025

    @wesleytodd
    Member

    Oh cool, I forgot about that one. Lets close this then and use that for any further discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions