Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Long paths and Streamline cache #358

Open
ghost opened this issue Mar 28, 2017 · 1 comment
Open

Long paths and Streamline cache #358

ghost opened this issue Mar 28, 2017 · 1 comment
Labels

Comments

@ghost
Copy link

ghost commented Mar 28, 2017

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.

@ghost ghost added the bug label Mar 28, 2017
@bjouhier
Copy link
Member

Hi Eric,

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant