Alex Nordlund

Reading the bug it sounds like we should be safe though? We're putting node first on the path so the shebang should work Although based on description it sounds like...

The reason it's saying that is because you need a node built for your operating system (technically libc) So if you try running the same build but in a VM...

Up to this point I thought that yarn was the sane alternative to npm, but the way to change to yarn 2 is bizarre. I haven't tested this myself, but...

Some of these would be specific to your environment, but to get rid of CrossOrigin you might be interested in something like [webpacks devServer.proxy](https://webpack.js.org/configuration/dev-server/#devserverproxy) to serve your JS and proxy...

yeah it sounds like we're going to have to look into how we can support yarn 2. but their setup seems pretty bizarre to me, I don't understand why they...

I'll have to get back to you in regards to the unofficial node, but to work around this quickly you could download and install the unofficial node manually (make sure...

Can be disabled with `NPM_CONFIG_AUDIT`

Setting the `ENV` on the entire workflow didn't help and neither did adding a `.npmrc` with `audit = "false"`

We do have ARM support so I guess it's not entirely out of the question to autodetect and handle it, though I don't know how we'd detect musl, I tried...

`NpmProxy_integTest` fails consistently for me locally, first run of `install packages using proxy` fails, second works. If I replace `proxyMockServer = startClientAndServer(PortFactory.findFreePort())` with any port at all, both tests pass