Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

So do I actually just need to let it run for literal days?

It should be xfailed with an associated issue

Shouldn't need to download 400MB to run a test

I lied, but still
```
$ du -sh .pants.d/resolve/node
217M	.pants.d/resolve/node
```

Which implies I did manage to download anything

That download size really shouldn’t be an issue, I have pretty good internet at home

And my network usage is being underutilized if anything

I don’t know what `npm install` is taking so long doing, but it’s not the download.

You might try `./pants test.node contrib/node/examples::` in isolation until it works

If the Node stuff is using ~/.npm or ~/.cache/pants/... in any way, getting past this on its own should be a shared victory with the release script

`npm_config_loglevel=verbose ./pants ...` might be revealing

And the Node contrib is using `~/.npm` so you will be OK if you can get this thing to run once.  I see from the verbose npm output:
```
npm verb etag <https://registry.npmjs.org/defined> from cache
                       npm verb get saving defined to /home/jsirois/.npm/registry.npmjs.org/defined/.cache.json
```

<@U053HHEDG>: FYI: The CHANGELOG needs a fair bit of updating

<@U04S45AHA>: that environment variable might have been the magic I needed to figure this out, testing a hypothesis now.

Yup, that was it, it’s actually getting past `[contrib/node/examples/src/node/web-build-tool]` and moving on to other node installs.

I apparently need to be on my corporate VPN for npm install to work.

Which I did not realize, since this is an open-source project.