Just leaving this as a PSA. It was hard to find for me so thought I'd reshare.

I was using this plugin, but it breaks in newer versions (I think). I would suggest folks switch to using Netlify's recommendations here: https://answers.netlify.com/t/support-guide-handling-code-splitting-issues-on-netlify/113158

I used option 1, seems to do the trick.

rmdir() with recursive: true has been deprecated by Node.js.

Would it be possible to either:

• Use rm() instead with recusive: true? This would require setting the package.json engines.node to >=14.14.0.
• Use a library like del or rimraf?

utils.cache has a ttl option. Would this work for this plugin?

Using binaries like cp or rsync does not work for builds triggered with Netlify CLI. Those builds are run on the user's machine, which might not have cp and/or rsync installed, especially on Windows.

Would using a core Node.js fs.* method or a library like cp-file or cpy be an option instead?

Crawling the publish directory might be slow for some big sites. There might be a few opportunities of optimizing it:

• Each readdir already performs a stat syscall, so doing it again in

  netlify-plugin-ttl-cache/src/index.js

  Line 21 in 54127d8

  const { mtime } = await stat(file);

  might be redundant
• If no exclude input is specified, there is no need to perform a test() on the filename. Even though the default regular expression a^ should be fast and never match, it might become more expensive when performed thousands of times.
• Directories part of exclude might not need to crawled

There might also be some potential bugs with the directory crawling. For example, if a file was a symlink to one of its parent directory, would the crawline keep running until memory is exhausted?

I am wondering whether using a tried-and-tested library like readdirp might help fix all of this, and also simplify the code? What are your thoughts?

The path input specifies the publish directory.

At the moment, this defaults to build. However, it would be better to default to the site's publish directory, which is available at constants.PUBLISH_DIR.