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 to c:\Users\WORMSS\code < because I am lazy and don't want to type the full path all the time
- config prefix
c:\\program files\\nodejs
- package location:
c:\Users\WORMSS\code\@wormss\genstack
- symlink directory
c:\program files\node to c:\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
Steps:
- navigate to
c:\code\@wormss\genstack (note, the shortcut of c:\code, not the full path through users)
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 of c:\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 from c:\program files\nodejs to c:\ but mistakenly it taken it to c:\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 testing c:\code but is actually hitting c:\Users\WORMSS\AppData\Roaming\Code and passing a test?? Maybe? no idea..
Current Behavior:
I am creating a
npm linkto a package I am creating, andnpm linkcreates a link to the wrong location.Expected Behavior:
Create a link to the correct folder.
Steps To Reproduce:
Environment:
c:\codetoc:\Users\WORMSS\code< because I am lazy and don't want to type the full path all the timec:\\program files\\nodejsc:\Users\WORMSS\code\@wormss\genstackc:\program files\nodetoc:\Users\WORMSS\AppData\Roaming\nvm\v15.9.0< because that is where nvm installs the versions but NVM isn't required to setup the symlinkSteps:
c:\code\@wormss\genstack(note, the shortcut of c:\code, not the full path through users)npm link< this makes genstack in globalc:\users\WORMSS\AppData\Roaming\code\@wormss\genstackinstead ofc:\code\@wormss\genstackEnvironment:
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)
c:\codewith\codeo..\..\to get fromc:\program files\nodejstoc:\but mistakenly it taken it toc:\users\WORMSS\AppData\Roaminginstead?c:\Users\WORMSS\AppData\Roaming\CodeVSCode, but maybe npm is testing..\..\codethinking it's testingc:\codebut is actually hittingc:\Users\WORMSS\AppData\Roaming\Codeand passing a test?? Maybe? no idea..