nuxt: too many open files on build

@camhart @danielroe I wanted to share the resolution we found for the EMFILE: too many open files error we encountered while building the project. The issue appeared only on the Windows machine.

The issue was caused by using extremely broad patterns in tailwind.config.js file, specifically: ./*.html These patterns were scanning a large number of files, including those in the node_modules folder, causing the file limit to be exceeded. To resolve this issue, we refined the patterns in tailwind.config.js file to target only the necessary files and folders in the project. This change significantly reduced the number of files being processed, and the EMFILE error disappeared. Another positive effect was, that build speed was significantly increased. 🚀 I hope this solution helps others who may be facing similar issues!💪

https://tailwindcss.com/docs/content-configuration#configuring-source-paths

I also hit this issue recently, and found something of a workaround.

I’m using docker, so the solution was to add this option to the docker build command when building: --ulimit nofile=5000:5000. If you’re using WSL, you will need to manually increase your nofile limit.

Explanation

The EMFILE: too many open files error comes from the kernel when you try to open too many files at once as an individual user. This normally isn’t an issue if the default limit is very high or unlimited, but containerized environments and some distros will limit the default to 1024 for non-privileged containers. This includes WSL/Ubuntu.

See the following stackoverflow answers for more details.

https://stackoverflow.com/a/21070580/2351110 (linux and WSL) https://stackoverflow.com/a/43265189/2351110 (docker)

@danielroe No not really, it was fixed 3 releases after this issue