TanStack / TanStack/router

Tanstack start dev server fails to start when debugger attached in Webstorm

Open
#6,621 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.1k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
143

Description

Which project does this relate to?

Start

Describe the bug

Current behavior

  1. Run pnpm dev with WebStorm debugger attached
  2. Console reports ready, but all HTTP requests return 503 "Node env runner worker is unavailable"
  3. No errors, no crashes in the console but the web app does not load properly
Your Example Website or App

git clone https://github.com/lionelhorn/tanstack-start-webstorm-repro

Steps to Reproduce the Bug or Issue
git clone https://github.com/lionelhorn/tanstack-start-webstorm-repro
cd start-basic
pnpm install
  1. Open in WebStorm
  2. Create a run configuration for pnpm dev with debugger attached
  3. Run with debugger → open http://localhost:3000503 with "Node env runner worker is unavailable"
  4. Run without debugger → pages load normally
Expected behavior

http://localhost:3000 to return code 200 with website loaded
Using vscode to attach a debugger to pnpm dev works as expected

Screenshots or Videos

No response

Platform
  • WebStorm (2025.3.2 Build #WS-253.30387.83)
  • Node.js v24.11.1 (Windows 11 Pro x86_64)
  • Vite 7.3.1 (TanStack Start)
Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked tanstack-start-webstorm-repro repository: run pnpm install and compare pnpm dev with and without a WebStorm debugger attached. Trace the dev-server entry point responsible for the “Node env runner worker is unavailable” response, then verify that the debugger-attached run serves http://localhost:3000 with HTTP 200 instead of 503.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript, vite
Domain
backend, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.