Skip to content

meta: npm v4 tracking issue #8977

Closed
Closed
meta: npm v4 tracking issue#8977
Assignees
jasnell
Labels
discussIssues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.npmIssues and PRs related to the npm client dependency or the npm registry.

Description

@jasnell
jasnell
opened on Oct 7, 2016

@nodejs/ctc: npm inc is currently working on npm v4. The beta is expected to land on Oct 21st, stable on Oct 27th, two days after our scheduled ship date for v7. We likely won't get a PR for it until the 21st. Given that it's a semver-major update, we need to decide how to handle the update relative to the v7.0.0 release.

/cc @nodejs/npm @zkat @iarna

Activity

  1. jasnell
    added
    metaIssues and PRs related to the general management of the project.
    npmIssues and PRs related to the npm client dependency or the npm registry.
    discussIssues opened for discussion and feedback.
    on Oct 7, 2016
  2. jasnell
    added this to the 7.0.0 milestone on Oct 7, 2016
  3. jasnell
    self-assigned this
    on Oct 7, 2016

  4. Daniel15 commented on Oct 9, 2016

    @Daniel15
    Daniel15
    on Oct 9, 2016

    Do you know if there's a changelog or roadmap for npm v4? I haven't seen anything in their repo.

  5. kenany commented on Oct 10, 2016

    @kenany
    kenany
    on Oct 10, 2016
    Contributor

    @Daniel15 I believe the 4.x milestone covers the very least of what's to come.

  6. felipou commented on Oct 21, 2016

    @felipou
    felipou
    on Oct 21, 2016

    I think they gave up on that schedule. From the link @kenany posted:

    We're targeting a mid-February release of npm@4.0.0

  7. kenany commented on Oct 21, 2016

    @kenany
    kenany
    on Oct 21, 2016
    Contributor

    Released

    EDIT: (beta)

  8. bricss commented on Oct 21, 2016

    @bricss
    bricss
    on Oct 21, 2016
    Contributor

    It seems that they had some divine power and npm@4.0.0 going to be released very soon. There is only one issue in milestone to update documentation.

  9. jasnell commented on Oct 22, 2016

    @jasnell
    jasnell
    on Oct 22, 2016
    MemberAuthor

    @nodejs/ctc ... Given that v7.0.0 will be released in 3 days and we still do not have a PR that we can use to test npmv4 in core, I'm going to pull this off the v7.0.0 milestone. Hopefully we'll be able to do the bump up to v4 as semver-minor in a v7.x soonish...

  10. jasnell
    removed this from the 7.0.0 milestone on Oct 22, 2016

  11. watilde commented on Oct 25, 2016

    @watilde
    watilde
    on Oct 25, 2016
    Member

    To get feedbacks from users, this is still important since npm@3 will be under LTS and npm@4 will be the active latest version. Like @jasnell said, I also hope we'll be able to bump the version of npm to v4 as semver-minor update in Node v7

  12. zkat commented on Oct 26, 2016

    @zkat
    zkat
    on Oct 26, 2016
    Contributor

    Dropping a note that a lot of relevant discussion is happening over at #9284 for future readers <3

  13. targos
    closed this as completedon Jan 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

discussIssues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.npmIssues and PRs related to the npm client dependency or the npm registry.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions