Very long path names cause ENAMETOOLONG errors when we try to write out their page data

Most file systems / OSs restrict the length of file names cause computers used to be weak sauce.

https://serverfault.com/questions/9546/filename-length-limits-on-linux/9548#9548

Generally to 255 bytes.

An obscure error someone can run into is they’ll create paths longer than this and when we try to write out the page’s page data, Node will crash with a mysterious ENAMETOOLONG.

We should just detect when a path is too long & shorten it within the limits.

We can use a simple algorithm that trims back the path name & hashes the trimmed off parts to preserve uniqueness.

To see a real-world example of this happening & an example algorithm go to https://github.com/gatsbyjs/gatsby/issues/20338#issuecomment-575930958

[KyleAMathews]

Or you probably suggest that Gatsby will save the page data to a valid path and map it internally with the right page?

yes, that 😃

[jlkiri]

Should be fixed by #21518. We probably should close this?