Release 6.11.1 #236
Closed
Release 6.11.1 #236
Conversation
This file contains 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
Make sure publishing with legacy username:password _auth works again
PR-URL: #120 Credit: @watilde Reviewed-By: @aeschright
PR-URL: #126 Credit: @watilde Reviewed-By: @aeschright
PR-URL: #138 Credit: @elidoran Reviewed-By: @aeschright
PR-URL: #144 Credit: @larsgw Reviewed-By: @aeschright
PR-URL: #145 Fixes: https://npm.community/t/4770 Credit: @larsgw Reviewed-By: @aeschright
…#140) PR-URL: #140 Credit: @greysteil Reviewed-By: @aeschright
PR-URL: #149 Credit: @zkat Reviewed-By: @aeschright
PR-URL: #151 Fixes: https://npm.community/t/npm-6-6-0-breaks-access-to-ls-collaborators/5101 Credit: @zkat Reviewed-By: @aeschright
PR-URL: #86 Fixes: https://npm.community/t/npm-install-for-package-with-local-dependency-fails/754 Credit: @iarna Credit: @jhecking Reviewed-By: @aeschright
Credit: @TooTallNate Fixes: zkat/make-fetch-happen#29
Prevent root-owned files in user-owned locations, and vice versa.
Don't use SUDO_UID and SUDO_GID. Just make the file match the folder it's being written into. The vast majority of the time, this will be the user's home directory, but if it's not, then we should not leave a user-owned file in a root-owned location. And, if running as root without SUDO_UID/SUDO_GID environs, but putting a config file in the user's home dir, then it's quite rude to leave it root-owned.
Do not leave a root-owned package-lock or npm-shrinkwrap file in the project root, where it will create problems when the user tries to update it later.
This seems to break every time a dependency is updated. Not sure why node 6 is any different than any other environment, but it's probably not worth debugging any further.
PR-URL: #235 Credit: @theberbie Close: #235 Reviewed-by: @isaacs EDIT(isaacs): Added test
PR-URL: #234 Credit: @claudiahdz Close: #234 Reviewed-by: @isaacs
|
This is already fixed in 6.11.2, I believe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey, i don't know where to open a solution for issue in latest npm (6.11.1) but i've found a solution for
"'find_dp0' is not recognized as an internal or external command"
and
" Cannot find module 'C:\node_modules\npm\bin\npm-cli.js'"
Please edit npm.cmd in C:\Program Files\nodejs and paste the below npm.cmd code so you can use npm again.
@echo off
SETLOCAL
IF EXIST "%dp0%\node.exe" (
SET "_prog=%dp0%\node.exe"
) ELSE (
SET "_prog=node"
SET PATHEXT=%PATHEXT:;.JS;=;%
)
"%_prog%" "%dp0%\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" %*
ENDLOCAL
EXIT /b
find_dp0:
SET dp0=%~dp0
EXIT /b