Too long file name, making it hard to work with package on linux (255 char max on a path)

[JostBaron]

When installing the package 'grunt-jsdoc', it installs this package as dependency, in this path:

<project-root>/node_modules/grunt-jsdoc/node_modules/ink-docstrap/

This creates the file

<project-root>/node_modules/grunt-jsdoc/node_modules/ink-docstrap/themes/paper/module-documents_probe.This%2520is%2520not%2520actually%2520a%2520class,%2520but%2520an%2520artifact%2520of%2520the%2520documentation%2520system.html

This filename has 214 characters alone for the path under the project root, leaving only 41 characters for the path to the project. If the path to the project has more than these 41 characters, the error npm ERR! Error: ENAMETOOLONG, open '<complete path>' is thrown.

The file system is ext4, so nothing old and dusty.

[perry-mitchell]

Has there been any progress on this? I'm encountering the same issue, and it seems many others are posting similar issues:

#103
krampstudio/grunt-jsdoc#116

I get something like: /node_modules/grunt-jsdoc/node_modules/ink-docstrap/themes/paper/module-documents_probe.This%2520is%2520not%2520actually%2520a%2520class,%2520but%2520an%2520artifact%2520of%2520the%2520documentation%2520system.html, which is obviously in error.

[bobholt]

This is due to the ink-docstrap dependency running docs against this line, which generates the filename causing the ENAMETOOLONG error:

https://github.com/terryweiss/docstrap/blob/master/fixtures/documents/probe.js#L1004

See also:

• ENAMETOOLONG on latest install krampstudio/grunt-jsdoc#142
• Error installing with npm #103

[joh-klein]

Why isn't this being fixed?

[gert-fresh]

npm ERR! ENAMETOOLONG: name too long, open '/home/xxx/xxx/xxx/test/node_modules/ink-docstrap/themes/paper/module-documents_probe.This%2520is%2520not%2520actually%2520a%2520class,%2520but%2520an%2520artifact%2520of%2520the%2520documentation%2520system.html'

I have this issue too, on an encrypted (ecryptfs) ext4 partition on Ubuntu 15.04.

[davidmaxwaterman]

This is blocking me too (worked-around by moving repo to /opt).

[gert-fresh]

Please review and/or merge: #114

[lukeapage]

This should be fixed in the 0.5.3 release (out now) - the file doesn't seem to be generated for me. I'm going to exclude the themes directory from npm because its just generated html for docs - not needed for publishing on npm.

Can someone verify?

[terryweiss]

I can confirm it is only for local docs in the event you are not connected and want to see the themes. I doubt it was ever really used.

[gert-fresh]

I can confirm too it's been fixed.