nodeJS - 未处理的“错误”事件

Question

每次启动npm start 时都会收到此错误，据我所知，这是由于同一端口上运行的进程所致，因此我必须使用netstat -nlp | grep 3000 搜索并终止该进程。

但是在每次文件更改时都这样做很不方便，我也有 nodemon 的错误可能导致它：[nodemon] app crashed - waiting for file changes before starting...

App.js：

var mongoose = require("mongoose");
var bodyParser = require("body-parser");
mongoose.Promise = require("bluebird");
var apiRouter = require('./routes/routes');
var express = require("express");
var app = express();

//raccourci pour bootstrap
app.use(bodyParser.urlencoded({
    extended: true
}));
app.use(bodyParser.json());
app.use(express.static('public'));
app.set('view engine', 'ejs');
//Ajout du slug course
app.use('/courses', apiRouter);

//Connexion à la bdd
mongoose.connect('mongodb://my_connection_string')
                .then(
                    console.log("CONNECTE !!!")
                );

app.listen(3000, function(){
    console.log("Bonjour !");
}); 

Answer 1

当你的应用崩溃时杀死猫鼬：

process.on("SIGINT", () => {
    mongoose.connection.close(() => {
        console.log("App is closing, ending mongoose connection");
        process.exit(0);
    });
});

虽然，您可能会遇到这个错误：

remy/nodemon #1025: Nodemon frequently leaves the child process running (detached)