3 ms·
Isn't the max path issue an operating system bug exposed because the tool you were using was designed to run on an OS without that bug?
by iends 10y ago
Isn't the max path issue an operating system bug exposed because the tool you were using was designed to run on an OS without that bug?
- baq 10y agoare you implying that design decision is good?
- zamalek 10y agoYou can't store an arbitrarily long path regardless of OS. EXT4 only pushes the value to 4096 - meaning that encountering this bug on Linux is only a matter of time. The unreasonably small value on Windows merely resulted in this boundary condition failing sooner. Code merely pushes electrons around, meaning that it has constraints firmly rooted in physics. So no: NPM runs in a universe (regardless of OS) and fails to account for the constraints of that universe by falling into unbounded recursion far too easily. This could have all been avoided by correctly applying graph theory and/or prior wisdom in regard to dynamically loading modules - which has existed for decades. Now we're forced to kludge it with reparse/symlink and that only works on file systems with these features.