VS Code中Node.js+Express应用调试启动后立即停止求助

Hey there, let’s figure out why your Express server is shutting down right after launching in debug mode instead of staying alive. I’ve dealt with this exact problem a few times, so here are the most likely fixes to walk through:

1. Make Sure Your Express Server Is Actually Listening #

The most common culprit here is forgetting to start the server with app.listen(). Without this, your Node process finishes executing the script and exits immediately—nodemon has nothing to watch!

Double-check your index.js for code like this:

const express = require('express');
const app = express();

// Your routes/middleware here

// Critical line - don't skip this!
app.listen(3000, () => {
  console.log('Server running on http://localhost:3000');
});

If this block is missing or commented out, add it back first.

2. Verify Dependencies Are Installed Correctly #

Nodemon and babel-node rely on specific dev dependencies. Run this command to make sure everything is in place:

npm install --save-dev @babel/core @babel/node nodemon

Also, if you’re using per-env, ensure it’s installed as a regular dependency:

npm install per-env --save

Missing dependencies can cause silent failures that make the process exit abruptly.

3. Check Your Babel Configuration #

Babel needs a valid config file to transpile your code properly. Create or update a .babelrc file in your project root with at least the basic preset:

{
  "presets": ["@babel/preset-env"]
}

If your Babel config is missing or invalid, babel-node will fail to compile your code, leading to an immediate process exit.

4. Inspect the Console Output for Errors #

Run your dev command again and watch the terminal closely:

npm run devStart

Look for any error messages—things like syntax errors, missing modules, or permission issues will all cause the process to stop. If the output is too quiet, add verbose logging to nodemon:

nodemon --verbose --exec babel-node index.js

This will show you exactly what nodemon is doing and where it might be failing.

5. Simplify the Command to Isolate the Problem #

Let’s narrow down whether the issue is with nodemon, babel-node, or your code:

• First, try running the server without nodemon: babel-node index.js. If it still exits, the problem is with Babel or your Express code.
• If that works, try running nodemon without babel-node (if your code is ES5-compatible): nodemon index.js. If this stays running, the issue is with the interaction between nodemon and babel-node.

6. Test the start:development Command Directly #

Since your start command uses per-env, there might be a configuration issue there. Skip the middleman and run:

npm run start:development

If this works, check your per-env setup to make sure it’s correctly mapping the development environment to the right command.

Start with the first two checks—they’re the quickest to verify and solve 90% of cases like this. Let me know if you hit any specific errors in the logs!

内容的提问来源于stack exchange，提问作者SpeedRacer