| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Could you also s/varibles/variables while you're at it? :D
Sorry, something went wrong.
|
Ping @iarna LGTM, but the title exceeds 50 characters. Also the commit prefix should probably be tools:, or tools,test:. These are minor nits I can fix on landing if need be, though. :) |
Sorry, something went wrong.
|
Landed in f5445db with the above nits fixed |
Sorry, something went wrong.
Updated test-npm to use absolute paths for tmp/cache/prefix PR-URL: #3309 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Updated test-npm to use absolute paths for tmp/cache/prefix PR-URL: #3309 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
|
should this be added to LTS? /cc @jasnell |
Sorry, something went wrong.
|
It could be, but I'm not worried about this being necessary in npm@2. |
Sorry, something went wrong.
|
fair enough. I guess we can hold off on this assuming npm3 will not be backported |
Sorry, something went wrong.
|
@thealphanerd npm @ 3 is a breaking change. :) |
Sorry, something went wrong.
|
Don't see a pressing need to get this into lts
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This gives npm absolute paths to use for its cache, prefix and tmp folders. Using relative paths seems to work, but makes me feel veeery edgy, as we do sometimes run subshells with copies of npm and we do sometimes change the working directory in tests. It seems to me that using relative paths here is just asking for really hard to track down trouble.
r: @Fishrock123
r: @chrisdickinson