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
If LongPathsEnabled is enabled on Windows, is there guidance for getting long paths supported in Node.js as well? Or is there a bug tracking this 260+ characters long paths support in Node.js?
Context:
I am not sure if I'm understanding the details of internal Node.js support of long paths yet, but I do see this comment by @bzoz that "Node uses file namespace paths for file access. We do that so we do not get hit by the 260 path limit," - maybe this only applies to writeFile?
The
MAX_PATH
explanation and workarounds guide by @mousetraps seems like a nice set of workarounds and explanation, but seems outdated now (eg. mentions npm v3, doesn't mentionLongPathsEnabled
)If
LongPathsEnabled
is enabled on Windows, is there guidance for getting long paths supported in Node.js as well? Or is there a bug tracking this 260+ characters long paths support in Node.js?Context:
writeFile
?import
longnode_modules
paths Bug: Long node_modules plugin paths cannot be found on Windows eslint/eslint#17763It would be great to get support for long file paths on Windows in Node.js!
The text was updated successfully, but these errors were encountered: