Error 'Cannot read properties of undefined (reading external)' when running bun run dev with Nuxt 3.
Hey everyone! I'm facing an issue when trying to run my Nuxt project with
bun run dev. I created the project using npm create nuxt@latest -- -t ui --packageManager=bun, but when I run the dev command, I get the error below. It seems related to Nitro, but I'm not sure how to fix it. Has anyone encountered this or have any ideas on what might be causing it? Here's my environment:
- Operating System: Linux
- Node Version: v20.12.2
- Nuxt Version: 3.16.2
- CLI Version: 3.24.0
- Nitro Version: 2.11.8
- Package Manager: [email protected]
- User Config: devtools, modules, css, future, compatibilityDate
- Runtime Modules: @nuxt/[email protected], @nuxt/[email protected], @nuxt/[email protected], @nuxt/[email protected]
Here's the full error:
Any help would be greatly appreciated! Thanks!3 Replies
Hi @Hermes Alves. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the error you're experiencing with Bun and Nuxt 3, this appears to be related to issues between Bun as a runtime and Nitro (Nuxt's server engine). Several similar issues have been reported in the Nuxt GitHub repository.
Possible Solutions
1. Use Polling for File Watchers
The most common workaround for Bun + Nuxt 3.16.x issues is to configure your watchers to use polling in your
nuxt.config.ts:
This solution was suggested in Nuxt 3.16.0 - Unable to run the DEV Server with bun and has helped many users.
2. Set Environment Variable for Nitro
If you're on Windows or experiencing socket-related errors, you can try setting the NITRO_NO_UNIX_SOCKET environment variable as mentioned in Nuxt 3.16.0 - Unable to run dev server with bun.
3. Clean Installation
Try removing your lockfile, node_modules, .nuxt, and .output directories, then reinstall dependencies:
This approach helped users in this issue with similar Nitro-related errors.
4. Try Without --bun Flag
If possible, try running without the --bun flag:
Instead of:
This might use Node.js as the runtime instead of Bun, which could avoid the compatibility issues.
5. Update to Latest Versions
Make sure you're using the latest versions of Bun and Nitro. Recent releases of Nitro (2.11.6+) have included fixes for Bun compatibility issues.
Additional Context
There have been several reported issues with Bun and Nuxt 3.16.x, particularly related to file watching, sockets, and Nitro server initialization. The Nuxt team is aware of these issues and has been working on fixes in recent releases.
If none of these solutions work, you might want to consider temporarily using npm or yarn as your package manager until these compatibility issues are fully resolved.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@727670710033580124> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
Hey, thanks for the suggestions! Unfortunately, none of the options worked for me. I tried all three:
1. Use Polling for File Watchers: I added the
watchers and nitro.watchOptions with usePolling: true to my nuxt.config.ts as suggested, but I still get the same Cannot read properties of undefined (reading 'external') error when running bun run dev.
2. Set Environment Variable for Nitro: I set the NITRO_NO_UNIX_SOCKET environment variable (I’m on Linux, not Windows, but I gave it a shot anyway), and it didn’t make a difference—same error.
3. Clean Installation: I removed node_modules, .nuxt, .output, and the lockfile, then ran bun install again. After that, I tried bun run dev, but the error persists.
I’m still stuck with this issue. Any other ideas? Here’s my setup again for reference:
- Operating System: Linux
- Node Version: v20.12.2
- Nuxt Version: 3.16.2
- CLI Version: 3.24.0
- Nitro Version: 2.11.8
- Package Manager: [email protected]
Thanks for any further help!