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
The current cache mechanism uses the path name for the directory for the cache files and therefore can create very long paths which may exceed the 260 character path limit on Windows. Maybe very long paths should be abbreviated using a hash (or something similar). Example:
What problem did you encounter? Normally, node itself should not be bothered by long paths (other tools like editors may but cached files are not really intended to be manipulated directly). A cheap workaround is to move your files (cache location and source) closer to the root. A more expensive one is to buy a mac 😄.
I did not use a hash because I did not want to lose the original path info (for easy debugging).
The current cache mechanism uses the path name for the directory for the cache files and therefore can create very long paths which may exceed the 260 character path limit on Windows. Maybe very long paths should be abbreviated using a hash (or something similar). Example:
C:\Acme\Azilaute\azilaute_NODE0QAGXV11\azilaute\cache\qualityadmin\v2.0.25-callbacks-218350100\D____Acme__Azilause__szilaute_NODE0QAGXV11__azilause__bin__shadow-modules__win32-x64-v8-4.5__node_modules\azilaute-code\node_modules\streamline-locale\lib\locale.map
Here this directory name itself has 104 characters.
The text was updated successfully, but these errors were encountered: