You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like some npm modules are attempting to hack the file system of windows - once I run npm install I am unable to delete them again due to long-path constraints of windows.
Is there any fix for this? Why is it possible for a npm module to create folders recursively and unlimited?
The text was updated successfully, but these errors were encountered:
This is not a hack, but a known issue with old npm and Windows with many nested dependencies.
This is solved by npm3, which no longer nest dependencies. See npm/npm#3697
What @Florian-R said, it's a workaround for the 260 character path limit on Windows. You can still delete the directories through their long name. See also path._makeLong(filename).
It seems like some npm modules are attempting to hack the file system of windows - once I run
npm install
I am unable to delete them again due to long-path constraints of windows.Is there any fix for this? Why is it possible for a npm module to create folders recursively and unlimited?
The text was updated successfully, but these errors were encountered: