https://artosalminen.github.io/series/vite/ Recent content in Vite on Arto's dev time by-products Hugo -- gohugo.io en Wed, 02 Jul 2025 00:00:00 +0000 https://artosalminen.github.io/posts/how-to-resolve-vitest-mui-icons-emfile-too-many-open-files-error/ Wed, 02 Jul 2025 00:00:00 +0000 https://artosalminen.github.io/posts/how-to-resolve-vitest-mui-icons-emfile-too-many-open-files-error/ <p>If you&rsquo;re running your Vitest suite on a high thread count machine—like an 8-core or 16-core development machine—you may encounter a frustrating error that looks like this:</p> <pre tabindex="0"><code>EMFILE: too many open files </code></pre><p>This issue can be cryptic at first, especially when your system doesn&rsquo;t seem anywhere near running out of resources. But the root cause might not be in your system limits—it could be in your import statements.</p> <h2 id="the-unexpected-culprit-named-imports-from-mui">The Unexpected Culprit: Named Imports from MUI</h2> <p>In my case, after hours of digging, I discovered that the error was caused by using <strong>named imports</strong> from Material UI (MUI) components and icons. These named imports, when used across many test files, were triggering Vitest to open an excessive number of files behind the scenes.</p>