N
Nuxt3w ago
scrongly

Cannot start nuxt: EMFILE: too many open files

Keep getting this error on a fresh install of nuxt 3 and storyblok using the storyblok starter. I've never seen this error before. The codebase has no pages, no plugins (aside from SB and tailwind, which came with it), no composables etc. First time seeing such an error while working with Nuxt or SB. Has anyone encountered this before?
11 Replies
kapa.ai
kapa.ai3w ago
Hi @scrongly. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- This error is related to the "too many open files" issue that some users have encountered when working with Nuxt. Based on the information provided in the knowledge sources, here are some insights and potential solutions: 1. Antivirus interference: The issue might be caused by antivirus software scanning files during the build process. As mentioned in the GitHub issue comments (https://github.com/nuxt/nuxt/issues/12376), antivirus software can cause many files to be opened simultaneously, leading to this error. You could try adding exceptions to your antivirus for your project directory to see if it resolves the issue. 2. Package manager: One user reported solving the problem by switching from Bun to npm or pnpm. If you're using Bun, you might want to try using a different package manager like npm or pnpm to see if it resolves the issue GitHub issue comment (https://github.com/nuxt/nuxt/issues/12376). 3. Operating system limits: Although not explicitly mentioned in the provided sources, this error can sometimes be related to operating system limits on the number of open files. You might want to check your OS settings and increase the limit if possible. 4. Fresh install: Since you mentioned this is happening on a fresh install, it's possible that there might be an issue with the Storyblok starter or its dependencies. You could try creating a basic Nuxt 3 project without the starter to see if the problem persists. If none of these solutions work, you might want to: 1. Check for any recent issues in the Nuxt or Storyblok repositories related to this error. 2. Try clearing your node_modules folder and package-lock.json (or yarn.lock) file, then reinstalling dependencies. 3. Ensure you're using the latest stable versions of Nuxt 3 and the Storyblok integration. If the problem continues, it would be helpful to provide more details about your development environment (OS, Node.js version, package manager version) and the exact steps to reproduce the issue when seeking further assistance from the Nuxt or Storyblok community. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
kapa.ai
kapa.ai3w ago
<@335863452692119552> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
scrongly
scronglyOP3w ago
^ already done all of this.
Mathieu
Mathieu3w ago
I have the same problem, macOS up-to-date and M1 chip. Any clue ?
Jure
Jure3w ago
Me too. On fresh Nuxt install. M3
productdevbook
same problem today m1
productdevbook
GitHub
EBADF error with Nuxt 3 and Vite on macOS, requiring esbuild versio...
Environment Operating System: Darwin Node Version: v21.7.2 Nuxt Version: 3.13.2 CLI Version: 3.15.0 Nitro Version: 2.9.7 Package Manager: [email protected] Builder: - User Config: default Runtime Modules:...
Ducky
Ducky3w ago
Same issue on M3 chip
taunoha
taunoha3w ago
For me, disabling the devTool helped...
devtools: { enabled: false },
devtools: { enabled: false },
Ducky
Ducky3w ago
With devtools off it's working for me to
scrongly
scronglyOP3d ago
I still haven't figured out what was causing this issue. Ended up having to create a completely fresh build using the storyblok starter. The trick was not to update the nuxt module. I've a feeling the SB nuxt module hasn't updated their nuxt version, but I honestly haven't had time to check.
Want results from more Discord servers?
Add your server