Open szatanjl opened 2 years ago
Hey, I have an external FAT32 HDD drive on my Ubuntu, and I have some similar problems. Npm install not work on FAT32 At first I find that npm install $Something --no-bin-links did work, but it seem to be kinda easy to forget. And then I try to see if some sort of option of no-bin-links exist, so I type npm config ls -l Then the option bin-links = true appear in the list, so I should just set it to false to test. Now type npm config set bin-links false And now npm Install in my external hard drive FAT32 work, but I'm still a novice so it would be nice if someone tell me if there is some source of consequences. But for now it work.
And before that I did set the globalconfig to "media/$MY_NAME/$HDD_Drive_name" , but i'm not sure if that is really neccessary, just document the stuff I did.
I also faced the same issue on exFAT SSD. Is there any solution for this?
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I have started a react-native project. But instead of keeping files on hard drive I wanted to keep everything on a USB drive. I have formated it to FAT32. And so problem starts.
npm install
by default creates symlinks to binaries innode_modules/.bin/
, but FAT32 does not support symlinks. So runningnpm install
fails. Searching/googling around the internet the only thing I have found is to add--no-bin-links
argument. Unfortunatelly that does not solve anything. Yesnpm install
works, but everything after that fails. Runningnpx react-native
for example ends with error that command cannot be found. Which is to be expected - there is nonode_modules/.bin/
because of--no-bin-links
.I decided to look around the code of npm for solutions. I have found that there is a special case made for Windows to create shims (shell, powershell, cmd files) instead of symlinks (look
node_modules/bin-links/lib/link-bins.js line 4
. And also I found that I can cheat this isWindows check using env variable__TESTING_BIN_LINKS_PLATFORM__
(looknode_modules/bin-links/lib
line 1).And so for now I have added
export __TESTING_BIN_LINKS_PLATFORM__=win32
to my env and this way I have tricked npm into creating shell scripts instead of symlinks, and it works perfectly. I cannpm install
onto FAT32 USB drive. I can runnpx <commands>
no problem.But that is a hack/workaround, not a proper solution.
Expected Behavior
I would suggest to add new argument to
npm install
command. Something along the lines--prefer-bin-shims
that would then make npm create shell scripts instead of symlinks on Linux systems. The code for making those shell scripts is already there, and it works perfectly on my setup. The only thing missing is a command line option.Steps To Reproduce
npm install
npm install --no-bin-links
npx react-native
Environment
cache = "/tmp/szatan/npm" prefix = "/tmp/szatan/.npm"
; node bin location = /usr/bin/node ; cwd = /home/szatan ; HOME = /home/szatan ; Run
npm config ls -l
to show all defaults.