cli
cli copied to clipboard
[BUG] npm link confused by symlinks (windows)
Current Behavior:
I am creating a npm link
to a package I am creating, and npm link
creates a link to the wrong location.
Expected Behavior:
Create a link to the correct folder.
Steps To Reproduce:
Environment:
- symlink directory:
c:\code
toc:\Users\WORMSS\code
< because I am lazy and don't want to type the full path all the time- See (1) in image
- config prefix
c:\\program files\\nodejs
- See (2) in image
- package location:
c:\Users\WORMSS\code\@wormss\genstack
- See (3) in image
- symlink directory
c:\program files\node
toc:\Users\WORMSS\AppData\Roaming\nvm\v15.9.0
< because that is where nvm installs the versions but NVM isn't required to setup the symlink- See (4) in image
Steps:
- navigate to
c:\code\@wormss\genstack
(note, the shortcut of c:\code, not the full path through users)- See (3) in image
-
npm link
< this makes genstack in global- See (5) in image
- You will see it has made a link to
c:\users\WORMSS\AppData\Roaming\code\@wormss\genstack
instead ofc:\code\@wormss\genstack
Environment:
OS: Windows 10 Node: 15.9.0 npm: 7.5.3
My thoughts (though I know nothing about what it is trying to do internally)
- Possibly a root problem? Mistaking
c:\code
with\code
o - Possibly a relative path problem? Mistakenly trying to do
..\..\
to get fromc:\program files\nodejs
toc:\
but mistakenly it taken it toc:\users\WORMSS\AppData\Roaming
instead? - The only other coincidence I see, is that I do have a 'code' folder in
c:\Users\WORMSS\AppData\Roaming\Code
- But this has nothing at all to do with my code or nvm or npm or node.
- I think this is to do with
VSCode
, but maybe npm is testing..\..\code
thinking it's testingc:\code
but is actually hittingc:\Users\WORMSS\AppData\Roaming\Code
and passing a test?? Maybe? no idea..
Looks like a legitimate bug; We'll dig in on this (seems like it could be caused by linking to a symlink)
Just because this has been stale for a little while.. Has there been able update or traction with this bug?
Hello, Coming up to 2 years on this "Priority 2 bug" ? Just wondering if there is anything I should be doing to help speed this along?