Nuxt v5 with TUI error and terminal hangs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, nuxt, typescript
- Domain
- cli
Research direction
Start by running the reported nuxi.mjs dev --envName web command with --trace-warnings and compare the output with TUI disabled. Trace the warning from srvx/dist/adapters/node.mjs at line 125, where the reported stack reaches pipeline, and determine whether the repeated ServerResponse close listeners correlate with the terminal hang. Done means the cause is reproducible and the TUI no longer hangs after navigation.
Written by the indexing model from the issue text.
Description
I'm testing Nuxt v5 on a huge repo using Nuxt 4.6.3, after some minimal changes at nitro configuration, the app is running, but the TUI hangs after a few navigations:
node error at TUI
System Info (cannot paste TUI info):
- Operating system :
Windows 10.0.19045 - CPU :
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 cores) - Node.js version :
v24.21.0 - nuxt/cli version :
4.0.1-2610292127-cd8f364 - Package manager :
[email protected] - Nuxt version :
5.0.0-2610292252-da55a91 - Nitro version :
3.0.261029-rc - Builder :
[email protected] - Config :
$admin,$android,$production,$web,app,compatibilityDate,components,css,devtools,experimental,fonts,future,i18n,modules,ssr,vitalizer,vite,vuetify - Modules :
[email protected],@pinia/[email protected],@nuxt/[email protected],@nuxtjs/[email protected],@unocss/[email protected],[email protected]
Running nuxi manually with --trace-warnings, this is the error:
node --trace-warnings ./node_modules/@nuxt/cli/bin/nuxi.mjs dev --envName web
15:08:06 GET /viviendas/10/grupo-humano (node:21328) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [ServerResponse]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
at genericNodeError (node:internal/errors:986:15)
at wrappedFn (node:internal/errors:540:14)
at warnMaxListenersExceeded (node:events:602:13)
at _addListener (node:events:593:7)
at ServerResponse.addListener (node:events:616:10)
at eos (node:internal/streams/end-of-stream:297:10)
at pipe (node:internal/streams/pipeline:469:10)
at pipelineImpl (node:internal/streams/pipeline:374:25)
at node:stream/promises:31:5
at new Promise (<anonymous>)
at pipeline (node:stream/promises:20:10)
at IncomingMessage.onReadable (file:///D:/work/projects/fi2net/COLOMBIA/redimu/redimu-aps-1.0/redimu-aps-ui/node_modules/.pnpm/[email protected]/node_modules/srvx/dist/adapters/node.mjs:125:4)
at IncomingMessage.wrapper (node:events:639:12)
at IncomingMessage.emit (node:events:514:28)
at emitReadable_ (node:internal/streams/readable:845:12)
at process.processTicksAndRejections (node:internal/process/task_queues:89:21)
Disabling TUI the node error just disappears:
running nuxt dev server without TUI
- Dominant language
- TypeScript
- Stars
- 402
- Forks
- 125
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nuxt/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
dev: false "reachable from the network" warning when `devServer.host` is a `*.localhost` subdomainMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Domain / chatbot New
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Inist-CNRS/lodex#3861 ·
Maintainers usually reply within 1 day
-
area:agent-sdk area:docs documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#110914 ·
-
area/cli platform/windows type/bug version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
anomalyco/opencode#64631 · 1 comment ·
Maintainers usually reply within 1 day