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

Migration issues due to node version (devServer) #4513

Open
2 tasks done
klmhyeonwoo opened this issue Dec 12, 2024 · 1 comment
Open
2 tasks done

Migration issues due to node version (devServer) #4513

klmhyeonwoo opened this issue Dec 12, 2024 · 1 comment
Labels

Comments

@klmhyeonwoo
Copy link

Node.js Version

from v.14.21.3 / to 20.18.1

NPM Version

from v6.14.18 / to v10.8.2

Operating System

MINGW64_NT-10.0-22631 DESKTOP-8P14V2D 3.4.9-be826601.x86_64 2023-09-07 12:36 UTC x86_64 Msys

Subsystem

https

Description

Hello, I have a question. While migrating from node14 to node20, I encountered the 'EADDRNOTAVAIL' error.

In fact, this problem can be solved by opening the host for the development server I want to use, and it verifies that the host is open and then runs it. Obviously, on node14, it was executed immediately without this process. Does anyone know what has changed in relation to what I said above as node versions go up?

Minimal Reproduction

No response

Output

No response

Before You Submit

  • I have looked for issues that already exist before submitting this
  • My issue follows the guidelines in the README file, and follows the 'How to ask a good question' guide at https://stackoverflow.com/help/how-to-ask
@preveen-stack
Copy link
Contributor

The EADDRNOTAVAIL error in Node.js occurs when a program tries to bind a socket to an IP address or port that is not available or cannot be used.

Can you share full error log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants