Skip to content

Node version requirement #996

@fabiancook

Description

@fabiancook

I have previously made a PR to update engines to support node 22, but now node 23 is out, and node 24 is about to be active.

https://nodejs.org/en/about/previous-releases#release-schedule

Would it be worth setting just the minimum version, and allowing the upper version to be open?

Or, is there a requirement to have engines defined to begin with?

I'd be more than happy to make the PR each release, especially the LTS releases... but it almost seems like it could be all skipped and engines could be set as >=18 and done, with the assumption is forward engine compatibility, but not backwards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions