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

tools: test-npm fixes for npm3 #3489

Closed

Conversation

Fishrock123
Copy link
Contributor

I feel better about doing it this way.

replaces #3308

See: #3308 (comment)

cc @nodejs/build or anyone elase: any sign-off will do.

@Fishrock123 Fishrock123 added test Issues and PRs related to the tests. npm Issues and PRs related to the npm client dependency or the npm registry. tools Issues and PRs related to the tools directory. labels Oct 22, 2015
@Fishrock123 Fishrock123 force-pushed the test-npm-fixes-for-npm3 branch from f69b0a0 to 6c9938b Compare October 22, 2015 17:32
@rvagg
Copy link
Member

rvagg commented Oct 22, 2015

lgtm, get it done and we'll shake it out in an RC

Fishrock123 pushed a commit that referenced this pull request Oct 22, 2015
Refs: #3308
PR-URL: #3489
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Fishrock123 added a commit that referenced this pull request Oct 22, 2015
Refs: #3308
PR-URL: #3489
Reviewed-By: Rod Vagg <rod@vagg.org>
@Fishrock123 Fishrock123 force-pushed the test-npm-fixes-for-npm3 branch from 6c9938b to 9b88864 Compare October 22, 2015 17:51
@Fishrock123 Fishrock123 deleted the test-npm-fixes-for-npm3 branch October 22, 2015 17:51
rvagg pushed a commit that referenced this pull request Oct 22, 2015
Refs: #3308
PR-URL: #3489
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Fishrock123 added a commit that referenced this pull request Oct 22, 2015
Refs: #3308
PR-URL: #3489
Reviewed-By: Rod Vagg <rod@vagg.org>
@MylesBorins
Copy link
Contributor

should this be added to LTS?

/cc @jasnell

@Fishrock123
Copy link
Contributor Author

@thealphanerd no, this is only for npm@3. v4 uses npm@2.

@MylesBorins
Copy link
Contributor

@jasnell this is only useful for npm3... are we planning to backport that to lts?

@Fishrock123
Copy link
Contributor Author

No, it shouldn't be backported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants