Skip to content

Prevent accidentally dropping support for older Node.js versions in a non-major version bump #88

@sindresorhus

Description

@sindresorhus

Scenario: Your package is at version 1.1.0. You decide to drop support for Node.js 0.12. You later do other changes and then publish a minor release. You've now accidentally done a breaking change in a minor release. This happens all the time. And will happen a lot more now that maintainers are starting to drop support for Node.js 0.10 and 0.12.

We could check if the engine field is higher than the latest version, and if not a major release, throw an error.

Thoughts?

Idea from: npm/npm#13549 // @bajtos

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions