Error: getaddrinfo ENOTFOUND localhost with vite when wifi is disabled

[andykais]

Related to this existing issue, which generated a similar error for different reasons #16643, I found a case where I cannot develop a vite app when my wifi is disabled.

$ deno --version
deno 2.2.3+f3e9325 (canary, release, x86_64-unknown-linux-gnu)
v8 13.4.114.11-rusty
typescript 5.7.3

Running arch linux, with a wlp4s0 wifi device.

repro

This can be accomplished when creating a default sveltekit app:

$ deno run -RWE npm:sv@latest create svelte-app

starting the app with wifi disabled creates the following error:

$ deno task dev
error when starting dev server:
Error: getaddrinfo ENOTFOUND localhost
    at __node_internal_captureLargerStackTrace (ext:deno_node/internal/errors.ts:93:9)
    at __node_internal_ (ext:deno_node/internal/errors.ts:246:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (ext:deno_node/internal/dns/promises.ts:32:17)
    at ext:deno_node/internal_binding/cares_wrap.ts:71:9

additional details

This does not occur with a default vite app however. The following command will create a sample vite app (which uses a svelte app template, fwiw) Update: this information was incorrect. This issue still occurs with the default vite templates

deno run -RWE npm:create-vite-extra@latest

[andykais]

this also occurs with latest deno canary:

deno 2.2.5+d07b7ea (canary, release, x86_64-unknown-linux-gnu)
v8 13.5.212.4-rusty
typescript 5.7.3

[nathanwhit]

cc @kt3k since you've worked on getaddrinfo recently

[kt3k]

Probably the regression caused by 2.1.5 (#25470).

@andykais Can you check if the issue exist with Deno 2.1.4?

#27936 switches back the getaddrinfo implementation to the original one. I think that PR would solve this issue.

[andykais]

hmm it looks like its still an issue in 2.1.4. This is my output after running deno upgrade --version 2.1.4

Task dev vite dev
A new release of Deno is available: 2.1.4 → 2.2.5 Run `deno upgrade` to install it.
error when starting dev server:
Error: getaddrinfo ENOTFOUND localhost
    at __node_internal_captureLargerStackTrace (ext:deno_node/internal/errors.ts:93:9)
    at __node_internal_ (ext:deno_node/internal/errors.ts:246:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (ext:deno_node/internal/dns/promises.ts:32:17)
    at ext:deno_node/internal_binding/cares_wrap.ts:78:9

I reran deno install after downgrading as well, in case that factored in

[kt3k]

hmm sounds strange.. maybe an independent issue.

Does your machine resolve localhost correctly with wifi disabled? What error does the script below report when wifi disabled?

await fetch("http://localhost");

[andykais]

here is the responses of hitting http://localhost (no server running on port 80) and hitting http://localhost:8000 (with python3 -m http.server running on port 8000)

> await fetch('http://localhost')
Uncaught TypeError: error sending request for url (http://localhost/): client error (Connect): tcp connect error: Connection refused (os error 111): Connection refused (os error 111)
    at async mainFetch (ext:deno_fetch/26_fetch.js:192:12)
    at async fetch (ext:deno_fetch/26_fetch.js:475:11)
    at async <anonymous>:1:22
> await fetch('http://localhost:8000')
Response {
  body: ReadableStream { locked: false },
  bodyUsed: false,
  headers: Headers {
    "content-length": "15265",
    "content-type": "text/html",
    date: "Thu, 27 Mar 2025 14:14:48 GMT",
    "last-modified": "Sun, 01 Jan 2023 08:05:54 GMT",
    server: "SimpleHTTP/0.6 Python/3.13.2"
  },
  ok: true,
  redirected: false,
  status: 200,
  statusText: "OK",
  url: "http://localhost:8000/"
}
>

this is on deno canary once again:

deno 2.2.5+9a28f0e (canary, release, x86_64-unknown-linux-gnu)
v8 13.5.212.4-rusty
typescript 5.7.3

[andykais]

So I did some more digging, and there are no issues with running deno & node:http, node:https or node:http2. The following works in both node and deno when wifi is disabled:

import * as http from 'node:http'
import * as https from 'node:https'
import * as http2 from 'node:http2'

function handleRequest(req, res) {
  res.writeHead(200)
  res.end('hello world')
}
http.createServer(handleRequest).listen(8080)
https.createServer(handleRequest).listen(8081)
http2.createServer(handleRequest).listen(8082)

this is just based off me trying to cold read the vite code and the limited stack trace I have to find out what kind of server it spins up

[andykais]

This does not occur with a default vite app however. The following command will create a sample vite app (which uses a svelte app template, fwiw)

I just retested this, and it does appear to be a problem with both

deno run -RWE npm:create-vite-extra@latest

and

deno run -RWE npm:create-vite@latest

with any settings. I will update the original issue description

[andykais]

So good news, this does appear to be fixed with latest deno canary. I am going to close this issue, I will update later with additional details on the version that appears to be working