Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

drop npm v1.x.x support #2622

Closed
boneskull opened this issue Dec 2, 2016 · 3 comments
Closed

drop npm v1.x.x support #2622

boneskull opened this issue Dec 2, 2016 · 3 comments
Labels
area: security involving vulnerabilities semver-major implementation requires increase of "major" version number; "breaking changes" type: chore generally involving deps, tooling, configuration, etc.

Comments

@boneskull
Copy link
Member

Currently we support npm v1.4.0 and greater. This will allow us to upgrade production dependencies (or dependencies thereof) which use carets in semver ranges. It should also allow scoped packages.

I'm not sure exactly in what version of npm v2.x.x scoped packages were introduced. I've asked @seldo if any data is available for npm v1.x.x usage.
@boneskull boneskull added the type: chore generally involving deps, tooling, configuration, etc. label Dec 2, 2016
@boneskull boneskull added this to the next-major milestone Dec 2, 2016
@boneskull
Copy link
Member Author

See #2621

@boneskull
Copy link
Member Author

It looks like the latest Node.js v0.10 installs npm v2.x.x by default.

I think we're OK to drop npm 1.x support. Probably still necessitates a major release.

@boneskull boneskull removed this from the next-major milestone Sep 27, 2017
@boneskull boneskull added area: security involving vulnerabilities semver-major implementation requires increase of "major" version number; "breaking changes" labels Sep 27, 2017
@boneskull
Copy link
Member Author

this will arrive as part of #3016.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: security involving vulnerabilities semver-major implementation requires increase of "major" version number; "breaking changes" type: chore generally involving deps, tooling, configuration, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@boneskull