En mi aplicación.js,
const app = require("express")(); const port = 3000; app.get("/", (req, res) => { res.send("hello world"); }); app.listen(port, () => { console.log("server running!"); });Este error se generó después de guardar/actualizar el archivo app.js,
(node:4196) UnhandledPromiseRejectionWarning: Error: Command failed: wmic process where (ParentProcessId=5740) get ProcessId 2> nul at checkExecSyncError (child_process.js:630:11) at execSync (child_process.js:666:15) at kill (C:\Users\SANTOSH\Desktop\nodesql\node_modules\nodemon\lib\monitor\run.js:337:26) at Function.run.kill (C:\Users\SANTOSH\Desktop\nodesql\node_modules\nodemon\lib\monitor\run.js:425:7) at Bus.<anonymous> (C:\Users\SANTOSH\Desktop\nodesql\node_modules\nodemon\lib\monitor\run.js:495:7) at Bus.emit (events.js:327:22) at restartBus (C:\Users\SANTOSH\Desktop\nodesql\node_modules\nodemon\lib\monitor\watch.js:228:7) at FSWatcher.filterAndRestart (C:\Users\SANTOSH\Desktop\nodesql\node_modules\nodemon\lib\monitor\watch.js:212:16) at FSWatcher.emit (events.js:315:20) at FSWatcher.emitWithAll (C:\Users\SANTOSH\Desktop\nodesql\node_modules\chokidar\index.js:540:8) (node:4196) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)archivo Package.json,
{ "name": "nodesql", "version": "1.0.0", "description": "", "main": "app.js", "scripts": { "start": "nodemon app.js" }, "keywords": [], "author": "", "license": "ISC", "dependencies": { "body-parser": "^1.19.0", "express": "^4.17.1", "mysql2": "^2.2.5", "sequelize": "^6.6.4", "sequelize-cli": "^6.2.0" }, "devDependencies": { "nodemon": "^2.0.9" } }Hoy actualicé mi npm a 7.19.1, después de eso recibo este error. De lo contrario, tiene que hacer algo con nodemon.
Tal vez la nueva versión de nodemon esté causando esto. Entonces, he degradado la versión a 2.0.7, ¡que funciona bien para mí!
npm uninstall nodemon npm install nodemon@2.0.7 --save-devVerifica nodemon -v, si no se reconoce nodemon, entonces npm install -g nodemon -> nodemon app.js
[ingrese la descripción de la imagen aquí] [1] [1]: https://i.stack.imgur.com/UbQLM.png
intente instalar nodemon versión 2.0.7 globalmente
primero instale la versión actual npm uninstall -g nodemon y luego escriba el comando npm i -g nodemon@2.0.7
al menos a mi me funciono :)