Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: EMFILE: too many open files, open error with version 3.3.3 #12003

Closed
last-Programmer opened this issue Sep 14, 2023 · 1 comment
Closed
Assignees

Comments

@last-Programmer
Copy link

last-Programmer commented Sep 14, 2023

What version of Tailwind CSS are you using?

3.3.3

What build tool (or framework if it abstracts the build tool) are you using?

postcss: 0.11.0, postcss-cli: 10.1.0

What version of Node.js are you using?

18.4.0

What browser are you using?

Chrome, Edge, FireFox

What operating system are you using?

Windows

Reproduction URL

Sorry unable to provide the reproduction url since our project is private. The error is not happening with tailwind version 3.3.2

Describe your issue

We have upgraded our project to tailwind 3.3.3 and we started getting this error

[Error: EMFILE: too many open files, open
errno: -4066,
code: 'EMFILE',
syscall: 'open',

The error is not happening with version 3.3.2

Thanks in advance for the help.

@RobinMalfait
Copy link
Member

Hey!

I have to close this as a reproduction was not provided. We also don't need access to a full private repo, but prefer small isolated reproductions where the issue is present. Trying to create a reproduction ourselves from the information in an issue drastically increases the amount of time it takes for us to provide a solution and if we have do that for every issue it’s impossible for us to keep up.

One thing you could check is if your content configuration contains a lot of files (e.g.: when you include node_modules or other large folders). If so, make sure they are not included in the content array.

Sorry, not trying to be dismissive and definitely want to fix the issue if there is one, but we have to be strict about this one or there's no way we could keep up with the number of questions we get and the quality of the library would suffer as a result. Hope that's understandable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants