问题描述
我正在尝试构建一个 nodeapi,为此我使用了一堆库,如 express、morgan、nodemon。
一切都正确安装,安装没有错误
当我尝试通过在 package.json 文件中更新来使用 nodemon 时,它会工作一次,然后拍摄 [正在显示?报告?一个] 意外错误
这里是终端上的错误
> node@1.0.0 start /root/Downloads/node
> nodemon server.js
[nodemon] 2.0.7
[nodemon] to restart at any time,enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node server.js`
Server Has Been Started
localhost:3000
events.js:353
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE: address already in use :::3000
at Server.setupListenHandle [as _listen2] (net.js:1318:16)
at listenInCluster (net.js:1366:12)
at Server.listen (net.js:1452:7)
at Object.<anonymous> (/root/Downloads/node/server.js:8:8)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47
Emitted 'error' event on Server instance at:
at emitErrorNT (net.js:1345:8)
at processticksAndRejections (internal/process/task_queues.js:82:21) {
code: 'EADDRINUSE',errno: -98,syscall: 'listen',address: '::',port: 3000
}
[nodemon] app crashed - waiting for file changes before starting...
这是我的 app.js 的样子
const express = require('express');
const app = express();
const morgan =require('morgan')
const employeeRoutes =require('./api/routes/employee');
const departmentRoutes =require('./api/routes/department');
app.use(morgan('dev'));
// Routes for api
app.use('/employee',employeeRoutes);
app.use('/department',departmentRoutes);
module.exports = app;
这是我的 server.js
const http=require('http');
const app =require('./app');
const port =process.env.PORT || 3000;
const server = http.createServer(app);
server.listen(port);
console.log('Server Has Been Started');
console.log('localhost:'+port);
我正在使用邮递员访问所有请求和响应。
我确实尝试使用 npm cache clean --force
但它不再起作用了。
解决方法
之前经历过类似的事情,只需尝试重新启动系统即可解决问题