Skip to content

docs: Add notes/disclaimers for upgrading the copy of node-gyp that npm uses#2585

Merged
rvagg merged 2 commits intonodejs:masterfrom
DeeDeeG:caveats-for-npm-upgrade-docs
Jan 6, 2022
Merged

docs: Add notes/disclaimers for upgrading the copy of node-gyp that npm uses#2585
rvagg merged 2 commits intonodejs:masterfrom
DeeDeeG:caveats-for-npm-upgrade-docs

Conversation

@DeeDeeG
Copy link
Contributor

@DeeDeeG DeeDeeG commented Jan 6, 2022

Checklist
Description of change

Add notes on npm version compatibility for methods to update the copy of node-gyp that npm uses.

Also mention that this is tested on npm 8, now that npm 8 exists. (Npm 8 is the same as npm 7 for purposes of these instructions.)

Lastly, add a note that one of the methods is simpler/more durable, but only functional for npm 6 and older.

Add notes on npm version compatibility for methods to update node-gyp.

Also mention that this is tested on npm 8, now that npm 8 exists.
(Npm 8 is the same as npm 7 for purposes of these instructions.)

Lastly, add a note that one of the methods is simpler/more durable,
if only functional for npm 6 and older.
@DeeDeeG DeeDeeG mentioned this pull request Jan 6, 2022
4 tasks
Use relative (current dir) links, rather than absolute web URLs.

Co-authored-by: Rod Vagg <[email protected]>
@DeeDeeG DeeDeeG force-pushed the caveats-for-npm-upgrade-docs branch from 369828a to 583abb4 Compare January 6, 2022 02:30
@DeeDeeG
Copy link
Contributor Author

DeeDeeG commented Jan 6, 2022

Made the links relative, thanks for pointing that out.

@rvagg
Copy link
Member

rvagg commented Jan 6, 2022

sgtm, as mentioned in the previous docs PR, we should try out faster merges on these doc PRs
thanks @DeeDeeG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants