Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

chore: add support for node 9.x#18964

Closed
MylesBorins wants to merge 7 commits intonpm:canaryfrom
MylesBorins:node-9
Closed

chore: add support for node 9.x#18964
MylesBorins wants to merge 7 commits intonpm:canaryfrom
MylesBorins:node-9

Conversation

@MylesBorins
Copy link
Copy Markdown

Seems like something that needs to be done 😄

@MylesBorins MylesBorins requested a review from a team as a code owner October 26, 2017 08:40
MylesBorins added a commit to MylesBorins/node that referenced this pull request Oct 27, 2017
MylesBorins added a commit to nodejs/node that referenced this pull request Oct 30, 2017
refs: npm/npm#18964

PR-URL: #16509
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
jasnell pushed a commit to nodejs/node that referenced this pull request Oct 30, 2017
refs: npm/npm#18964

PR-URL: #16509
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@depoulo
Copy link
Copy Markdown

depoulo commented Nov 1, 2017

Also, the error message should say "to a newer version of npm". Maybe you can just sneak this in here?
grafik

Update: Sorry my bad. In many cases, the error message is right. It's still wrong in this case though, but that should never happen in the first place.

@graingert
Copy link
Copy Markdown

you'll need to update the ci configs too...

@graingert
Copy link
Copy Markdown

@MylesBorins #19025

@MylesBorins MylesBorins changed the base branch from latest to canary November 1, 2017 21:36
@MylesBorins
Copy link
Copy Markdown
Author

@depoulo this patch should fix the exact problem

@graingert I've re targeted this to canary so no need to worry about the zlib

I've updated the travis yaml in another commit so you might be able to close #19025

Qard pushed a commit to ayojs/ayo that referenced this pull request Nov 2, 2017
refs: npm/npm#18964

PR-URL: nodejs/node#16509
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Qard pushed a commit to ayojs/ayo that referenced this pull request Nov 2, 2017
refs: npm/npm#18964

PR-URL: nodejs/node#16509
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@ilovezfs
Copy link
Copy Markdown

ilovezfs commented Nov 8, 2017

Does anyone have any idea what the ETA is for an npm 5.5.2 with support for node 9?

@ilovezfs
Copy link
Copy Markdown

@iarna @zkat any idea what the impediments are to a 5.5.2 release with the node 9 patches? That would be very helpful for the Homebrew formula, which is stuck on node 8 since it needs to work with the stock upstream npm.

@kenany kenany mentioned this pull request Nov 13, 2017
4 tasks
@zkat zkat force-pushed the canary branch 3 times, most recently from c8bbdbf to dc64380 Compare November 15, 2017 22:52
@MylesBorins
Copy link
Copy Markdown
Author

this is fixed by 6caf230

@mightyiam
Copy link
Copy Markdown

Hurrah! 🎆 🎉 and thanks!

addaleax pushed a commit to ayojs/ayo that referenced this pull request Dec 7, 2017
refs: npm/npm#18964

PR-URL: nodejs/node#16509
Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants