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

'Scala.js Com failed: ECONNREFUSED' for Com runs with Node.js 19 #27

Closed
carlosedp opened this issue Mar 31, 2023 · 3 comments
Closed

'Scala.js Com failed: ECONNREFUSED' for Com runs with Node.js 19 #27

carlosedp opened this issue Mar 31, 2023 · 3 comments
Labels
invalid This doesn't seem right

Comments

@carlosedp
Copy link

Apparently error reported in #12 returned recently.

Had to add the same workaround, adding List("--dns-result-order=ipv4first") as an argument to node and it fixed.

As I use mill, I added: def jsEnvConfig = T(JsEnvConfig.ExoegoJsDomNodeJs(args = List("--dns-result-order=ipv4first"))).

Don't know if the error is in this lib or mill itself but the workaround above worked.

@sjrd
Copy link
Member

sjrd commented Apr 1, 2023

From your setup it looks like you are not using this library, but exoego's fork. That fork never upgraded to scalajs-jsenv-podejs 1.2.1, which has the fix for #12.

Moreover, since it's Mill, apparently they themselves have a fork or a wrapper around the exoego env. For all I know they don't have the fix either.

Please file an issue in the appropriate repos. We can reopen here if there is evidence that it is still an issue for the library defined here.

@sjrd sjrd closed this as not planned Won't fix, can't repro, duplicate, stale Apr 1, 2023
@sjrd sjrd added the invalid This doesn't seem right label Apr 1, 2023
@kubukoz
Copy link

kubukoz commented May 30, 2023

I'm seeing this on Node.js 18, using sbt-scalajs. The metaproject tells me I'm using org.scala-js:scalajs-js-envs_2.12:1.4.0, which would be the latest. Shall I create an issue, or is it more likely that I'm doing something wrong?

@sjrd
Copy link
Member

sjrd commented May 31, 2023

If it is truly with scalajs-js-envs >= 1.2.1, it is likely a different issue, even if it has the same symptoms. Feel free to open a separate issue with a reproduction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants