镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

4.0.0 is not published to npm #1721

Closed
Closed

Description

@limonte

Activity

  1. limonte commented on Apr 17, 2019

    @limonte
    Author

    hm, 75cfae2

    The bump to v4.0.0 happened 2 years ago, but 4.0.0 was never published to npm.

    I have no idea what is happening with releasing of this package, can someone explain this mystery?

  2. limonte commented on Apr 17, 2019

    @limonte
    Author

    this issue results into node-gyp being vulnerable:

    image

  3. added a commit that references this issue on Apr 17, 2019
  4. JCMais commented on Apr 17, 2019

    @JCMais

    Related to #1717

    cc @nodejs/node-gyp

  5. shehi commented on Apr 19, 2019

    @shehi

    @limonte , this situation will be remedied?

  6. limonte commented on Apr 19, 2019

    @limonte
    Author

    @shehi I'm not the maintainer of this package. 2 years wasn't enough to run npm publish so I'd assume we'll need to wait a few more years.

  7. ChALkeR commented on Apr 24, 2019

    @ChALkeR
    Member

    I think this is now fixed per #1718 (comment) (thanks, @rvagg!).

    Closing this now, feel free to reopen and/or comment though.

    $ npm i node-gyp
    + node-gyp@4.0.0
    added 100 packages from 67 contributors and audited 156 packages in 5.265s
    found 0 vulnerabilities
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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