Build failure on WSL Ubuntu but not on OS/X

[rickmcgeer]

Describe the bug
I've tried to freeze https://github.com/engageLively/galyleo-dashboard, and the freeze works on my Mac but repeatedly fails on WSL, with the error message:

TypeError: Could not load https://jspm.dev/immutable@4.0.0-rc.12: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11457:11)
    at async WebDAVResource.read (file:///home/rick/lively.next/lively.resources/src/http-resource.js:232:17)
    at async fetchFile (/home/rick/lively.next/lively.freezer/src/resolvers/node.cjs:150:14)
    at async Object.load (/home/rick/lively.next/lively.freezer/src/resolvers/node.cjs:165:11)
    at async LivelyRollup.load (file:///home/rick/lively.next/lively.freezer/src/bundler.js:581:13)
    at async file:///home/rick/lively.next/lively.next-node_modules/rollup/2.70.2/dist/es/shared/rollup.js:22093:83
    at async Queue.work (file:///home/rick/lively.next/lively.next-node_modules/rollup/2.70.2/dist/es/shared/rollup.js:21677:32) {
  cause: SocketError: other side closed
      at TLSSocket.onSocketEnd (node:internal/deps/undici/undici:9689:26)
      at TLSSocket.emit (node:events:525:35)
      at endReadableNT (node:internal/streams/readable:1359:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '172.19.148.218',
      localPort: 34326,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 190,
      bytesRead: 0
    }
  },
  code: 'PLUGIN_ERROR',
  plugin: 'commonjs--resolver',
  hook: 'resolveId',

It was working fine until yesterday, but something is wrong today. I tried rebooting just in case it was system load. Same version of Lively

To Reproduce

1. Pull https://github.com/engageLively/galyleo-dashboard
2. On WSL, in the root directory, run npm build

Screenshots
If applicable, add screenshots to help explain your problem.

Setup
Please delete non-applicable items!

• Windows
• Linux

Version: Please paste the lively.next commit on which the problem occurred here (use the copy button of the Version Checker in the bottom left corner).
c725a77

[merryman]

Very strange, it appears to be a general issue with the network configuration of WSL here. Are you able to do a simple curl https://jspm.dev/immutable@4.0.0-rc.12?
It could also be something funny going on with jspm.dev. Since it is going to be shut down later this year, it could be that it is starting to degrade already. I am right now working on a PR that will alleviate that, but cant guarantee that this is the definitive cause.

[rickmcgeer]

Here's the response to a curl:

rick@LAPTOP-I4KMLV6U:~/lively.next/local_projects/engageLively--galyleo-dashboard/bin$ curl https://jspm.dev/immutable@4.0.0-rc.12
export * from "/npm:immutable@4.0.0-rc.12!cjs";
export { default } from "/npm:immutable@4.0.0-rc.12!cjs";
rick@LAPTOP-I4KMLV6U:~/lively.next/local_projects/engageLively--galyleo-dashboard/bin$

The code for galyleo is in transition now, so I won't be doing a build for a few hours, but I'll try it then.

[rickmcgeer]

This time, I ran the curl before the build, and this was the output:

curl https://jspm.dev/immutable@4.0.0-rc.12
export * from "/npm:immutable@4.0.0-rc.12!cjs";
export { default } from "/npm:immutable@4.0.0-rc.12!cjs";
rick@LAPTOP-I4KMLV6U:~/lively.next/local_projects/engageLively--galyleo-dashboard$ npm run build

> engageLively--galyleo-dashboard@0.2.0 build
> ./tools/build.sh

Setting V8 memory size limit to allow space for builds
Setting env vars for FLATN_PACKAGE_DIRS, FLATN_PACKAGE_COLLECTION_DIRS, FLATN_DEV_PACKAGE_DIRS for lively.next
Selected language: en
Path: ./tools/build-en.mjs
[lively.freezer]: Freezing in Progress
[lively.freezer]: Bundling...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
[BABEL] Note: The code generator has deoptimised the styling of /home/rick/lively.next/lively.morphic/text/icons.js as it exceeds the max of 500KB.
[lively.freezer]: Error fetching https://jspm.dev/immutable@4.0.0-rc.12. Retrying...
[lively.freezer]: Error fetching https://jspm.dev/immutable@4.0.0-rc.12. Retrying...

But this time, after a couple of retries, it worked!

I got the same response to the curl from my Mac

[rickmcgeer]

Frustratingly, this is an intermittent problem. It happened again, so I curled, got the usual 2-line response, then retried the build. The second build succeeded, though it did print the fetch error once.
This feels like a local problem on my box, but it also feels like one that might be replicated on other users' machines. The two fixes I can suggest are (1) use of node_modules a la Jupyter, and/or (2) a build server.