This repository was archived by the owner on Aug 11, 2022. It is now read-only.
Closed
Conversation
4 tasks
Contributor
|
@addaleax Thanks! This is a release week, so we'll pull this in and send up a PR probably ~friday |
Contributor
Author
|
Cool! That isn’t npm@5 by any chance, is it? I hear it’s fast. |
Contributor
|
@addaleax we have a regular npm@4 release on top of the public beta for npm5. I hear it's fast too but it's probably all marketing bullshit tbh. Can't trust these corporate types imo. New |
4 tasks
Contributor
|
This has been included in npm@5.0.0. Closing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Basically ran
npm i -S node-gyp@3.6.1, seems to have worked out well.