Not able to install framework (Windows 10, Node v20.11.1)

[EE2dev]

This is my environment:

• Windows 10 Enterprise
• Node v20.11.1

I am not able to set up framework on my work computer.
This is my error message when I run the Getting started example:

> dev
> observable preview

Observable Framework v1.9.0
↳ http://127.0.0.1:3000/

GET /
npm:@observablehq/plot → TypeError: fetch failed
    at node:internal/deps/undici/undici:12345:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/AZ_DATEN/_Allgemein/observable/framework/hello4/node_modules/@observablehq/framework/dist/npm.js:194:22 {
  cause: Error: getaddrinfo ENOTFOUND data.jsdelivr.com
      at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
    errno: -3008,
    code: 'ENOTFOUND',
    hostname: 'data.jsdelivr.com'
  }
}
TypeError: fetch failed
    at node:internal/deps/undici/undici:12345:11
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/AZ_DATEN/_Allgemein/observable/framework/hello4/node_modules/@observablehq/framework/dist/npm.js:194:22 {
  cause: Error: getaddrinfo ENOTFOUND data.jsdelivr.com
      at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
    errno: -3008,
    code: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'data.jsdelivr.com'
  }
}

[mbostock]

Probably because of a corporate proxy. Please upvote #1168 and see the issue for a workaround.

[mbostock]

It could be that your corporate proxy does not allow connections to planet4589.org.

[EE2dev]

From a browser I can load the files:

https://planet4589.org/space/gcat/tsv/tables/lv.tsv
https://planet4589.org/space/gcat/tsv/derived/launchlog.tsv

[mbostock]

Ah. The workaround in the observablehq.config.js file will only help Framework’s internal requests use your proxy (such as loading JavaScript libraries from jsDelivr). For data loaders, you’ll need similar workarounds to also make sure your data loader respects the HTTPS_PROXY environment variable — so in this case you’d need to modify src/data/launches.csv.js to also use your proxy if you want that request to work. Node.js doesn’t do this by default, though I see some indication in nodejs/node#8381 that it might be coming in a future release…

[EE2dev]

I will try to add the section

import {ProxyAgent, setGlobalDispatcher} from "undici";

const proxyAgent = new ProxyAgent({uri: process.env.https_proxy});
setGlobalDispatcher(proxyAgent);

to the data loader and reply tomorrow.
Thanks a lot for the immediate support!

[EE2dev]

Success! Thanks so much! 👍👍

To put the solution together:

1. Fix Errors when Framework internal requests uses proxy

→ Add three lines of code from #1168
to the file observable.config.js as workaround

2. Fix Errors when data loader uses proxy

→ Add the same three lines of code to the data loader (e.g. ./data/launches.csv.js) as workaround

import {ProxyAgent, setGlobalDispatcher} from "undici";

const proxyAgent = new ProxyAgent({uri: process.env.https_proxy});
setGlobalDispatcher(proxyAgent);