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.

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

standard install broken for npm@2? #408

Closed
gr2m opened this issue Feb 6, 2016 · 6 comments

Comments

@gr2m
Copy link

commented Feb 6, 2016

The latest update throws an error when running:
https://travis-ci.org/gr2m/initials/builds/107403864

After updating to npm@3, the error went away:
https://travis-ci.org/gr2m/initials/builds/107441491

Does standard require npm@3? I couldn't find any info on it.

Note that the above is just an example, I get the error in every package of mine, examples here, here and here and I got 15 more of these

@tunnckoCore

This comment has been minimized.

Copy link

commented Feb 6, 2016

Doh, why open new issue, when have #406 and #407?
I also have same problem, but will wait few hours.

It's strange to me that it fails on every version except v5, lol #406 (comment) make sense, lol.
https://travis-ci.org/tunnckoCore/acorn-strip-comments/builds/107431082

@gr2m

This comment has been minimized.

Copy link
Author

commented Feb 6, 2016

@tunnckoCore I’m very sorry, I looked for open issues quickly but that was pre- ☕️ me. Feel free to close as duplicate

@rstacruz

This comment has been minimized.

Copy link
Member

commented Feb 6, 2016

oh man, this happened on pnpm too when it was following npm@2 behavior more strictly.

@watson

This comment has been minimized.

Copy link
Member

commented Feb 6, 2016

@tunnckoCore Thanks for pointing out the duplicate issues.

Everyone: Let's move the discussion to #406

@gr2m

This comment has been minimized.

Copy link
Author

commented Feb 6, 2016

closing in favor of #406

@gr2m gr2m closed this Feb 6, 2016

@feross

This comment has been minimized.

Copy link
Member

commented Feb 7, 2016

This should be fixed in standard 6.0.3. Sorry for the trouble, folks!

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
5 participants
You can’t perform that action at this time.