init instability

[kanej]

Sometimes hardhat3 --init hangs on npm install once in a while (maybe 1/3rd to 1/2 of the tries), this is in typescript+node devcontainer on Windows.

• Running directly doesn’t hang, running through hardhat3 —init hangs.
• running it separately verbose works, maybe we should add —verbose to the hardhat3 init to check.
• particular npm install that always hangs is this:

npm install --save-dev "@ignored/hardhat-vnext@^3.0.0-next.15" "@ignored/hardhat-vnext-keystore@^3.0.0-next.11" "@ignored/hardhat-vnext-node-test-runner@^3.0.0-next.11" "@ignored/hardhat-vnext-network-helpers@^3.0.0-next.11" "@ignored/hardhat-vnext-viem@^3.0.0-next.10" "@types/node@^22.8.5" "forge-std@foundry-rs/forge-std#v1.9.4" "typescript@~5.5.0" "viem@^2.21.37"

This was reported by Marian when installing the Alpha within Docker on windows.

This is likely hard to reproduce and is likely showing up because of a network issue. However, the fact that running the instruction directly through npm works but our install halts suggests we might not be handling an error within --init when we call npm install.