{"version":"2.1.309","anchor":"dev-server-start-failures-get-specific-explanations","canonical_anchor":"dev-server-start-failures-get-specific-explanations","heading":"Clearer reasons when a dev server fails to start","tier":"notice","area":"Dev Server","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/dev-server-start-failures-get-specific-explanations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Clearer reasons when a dev server fails to start\n\nClaude Code now has specific explanations for four ways a dev server can fail to start, such as a port in use or packages not installed\n\n**What**\n\nA dev server is a program that runs your project locally while you work on it. Claude Code now has specific explanations for why one failed to start:\n\n- its port is already in use by another program\n\n- the project's packages are not installed, with a hint to run `npm install`\n\n- the start command was not found\n\n- the server stopped right after starting\n\n**Why**\n\nA named cause tells you what to fix, instead of only telling you that the server did not start.\n\n- Area: Dev Server\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}