Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node executor fails on rebuilds - Error: listen EADDRINUSE: address already in use #14072

Closed
goldylucks opened this issue Dec 31, 2022 · 4 comments
Assignees
Labels
blocked: retry with latest Retry with latest release or head. outdated scope: node Issues related to Node, Express, NestJS support for Nx type: bug

Comments

@goldylucks
Copy link

Current Behavior

Getting this error on rebuilds using the node executor in an express app:

Error: listen EADDRINUSE: address already in use

Expected Behavior

Shouldn't happen

Github Repo

No response

Steps to Reproduce

I can't pinpoint when it started happening or what's the root cause, but now even rolling back doesn't help.

Nx Report

$ nx report

 >  NX   Report complete - copy this into the issue template

   Node : 16.18.0
   OS   : darwin arm64
   yarn : 1.22.18

   nx : 15.4.1
   @nrwl/angular : Not Found
   @nrwl/cypress : 15.4.1
   @nrwl/detox : Not Found
   @nrwl/devkit : 15.4.1
   @nrwl/esbuild : Not Found
   @nrwl/eslint-plugin-nx : 15.4.1
   @nrwl/expo : Not Found
   @nrwl/express : 15.4.1
   @nrwl/jest : 15.4.1
   @nrwl/js : 15.4.1
   @nrwl/linter : 15.4.1
   @nrwl/nest : Not Found
   @nrwl/next : Not Found
   @nrwl/node : 15.4.1
   @nrwl/nx-cloud : 15.0.2
   @nrwl/nx-plugin : Not Found
   @nrwl/react : 15.4.1
   @nrwl/react-native : Not Found
   @nrwl/rollup : 15.4.1
   @nrwl/schematics : Not Found
   @nrwl/storybook : Not Found
   @nrwl/web : 15.4.1
   @nrwl/webpack : 15.4.1
   @nrwl/workspace : 15.4.1
   @nrwl/vite : 15.4.1
   typescript : 4.8.4
   ---------------------------------------
   Local workspace plugins:
   ---------------------------------------
   Community plugins:


### Failure Logs

_No response_

### Additional Information

_No response_
@AgentEnder
Copy link
Member

This is fixed in latest, can you try there?

@AgentEnder AgentEnder self-assigned this Jan 1, 2023
@AgentEnder AgentEnder added blocked: retry with latest Retry with latest release or head. scope: node Issues related to Node, Express, NestJS support for Nx labels Jan 1, 2023
@goldylucks
Copy link
Author

I actually moved to use vite for node, which would be great to have first class support to btw.

@PathToLife
Copy link

reporting running npx nx migrate from nx packages 15.4.0 to 15.4.2 did indeed fix this.

fix is on sahilpurav's pr #14023 🎉

@github-actions
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked: retry with latest Retry with latest release or head. outdated scope: node Issues related to Node, Express, NestJS support for Nx type: bug
Projects
None yet
Development

No branches or pull requests

3 participants