[BUG] npm install truncates paths at # #6809
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 9.x
work is associated with a specific npm 9 release
Release 10.x
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
npm install
appears to truncate its arguments after the first#
character, thus not finding the correct file when the path contains a#
.Expected Behavior
The only characters that should cause trouble in unix systems in paths are control characters (in particular, NUL) and forward/backward slashes (as path components). Under windows, further restrictions on valid paths exist, but they shouldn't prevent npm from finding files on valid paths.
Steps To Reproduce
Encountered while building the package https://aur.archlinux.org/packages/nodejs-nativefier in
/home/gesh/aur/9#deps/whatsapp-nativifier/nodejs-nativefier
, problem vanished when building in/home/gesh/aur/whatsapp-nativifier/nodejs-nativefier
.Log attached
Context-agnostic instructions:
http://registry.npmjs.org/nativefier/-/nativefier-52.0.0.tgz
to~/0#broken/
npm install ~/0#broken/*.tgz
~/0
mv ~/0#broken ~/fixed
npm install ~/fixed/*.tgz
Environment
The text was updated successfully, but these errors were encountered: