You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
% npx webpack-cli serve
[webpack-cli] Error [ERR_SERVER_ALREADY_LISTEN]: Listen method has been called more than once without closing.
at Server.listen (node:net:2008:11)
at READ_WRITE (/path/to/repo/cjs/node_modules/webpack-dev-server/lib/Server.js:3332:23)
at new Promise (<anonymous>)
at Server.start (/path/to/repo/cjs/node_modules/webpack-dev-server/lib/Server.js:3330:7)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Command.<anonymous> (/path/to/repo/cjs/node_modules/@webpack-cli/serve/lib/index.js:158:21)
at async Command.parseAsync (/path/to/repo/cjs/node_modules/webpack-cli/node_modules/commander/lib/command.js:935:5)
at async Command.<anonymous> (/path/to/repo/cjs/node_modules/webpack-cli/lib/webpack-cli.js:1356:13)
at async Command.parseAsync (/path/to/repo/cjs/node_modules/webpack-cli/node_modules/commander/lib/command.js:935:5)
at async WebpackCLI.run (/path/to/repo/cjs/node_modules/webpack-cli/lib/webpack-cli.js:1360:9) {
code: 'ERR_SERVER_ALREADY_LISTEN'
}
I'm not sure which library should be responsible for listening to the server, but at least in certain versions there is no problem on the webpack-dev-server side, so I reported it here.
and listen doesn't respect listenOptions, i.e. host and port (and based on current implementations that's expected 😕 ), I would say that this is a design api, before serve just return Server and doesn't run it, but now using serve it creates Server and run it
The
webpack-dev-server
example failed to run that integrated with latest@hono/node-server
.I'm not sure which library should be responsible for listening to the server, but at least in certain versions there is no problem on the
webpack-dev-server
side, so I reported it here.Enivironment
Steps to reproduce
Files
Command
My guess
It seems to break after the below PR landed.
The text was updated successfully, but these errors were encountered: