Skip to content

0.27.8 requires node ^18.17.0 || >=20.5.0 but nft intends to support node>=16 #457

@serhalp

Description

@serhalp

👋🏼 Hi folks!

This PR to upgrade node-pre-gyp (released in 0.27.8) indirectly bumped a transitive dependency nopt from 5.0.0 to 8.0.0.

and nopt@8.0.0 requires node ^18.17.0 || >=20.5.0.

However, @vercel/nft has package.json#engines#node of >=16:

nft/package.json

Lines 145 to 147 in 7fbb559

"engines": {
"node": ">=16"
},

TL;DR: nft intends to support node 16+ but no longer supports 16 to 18.16.0

I realize since nft is still on 0.x it can introduce breaking changes at any time, but I'm guessing this wasn't intentional! If it is, could we update the engines.node and note this in the release notes?

Thanks! Happy to open a PR if you all know what direction you want to take.

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