back to poking at adding type acquisition support to vscode.dev and finally fixed some issues that were making it slow. Tested with a huge package.json, yeah, it took a while. Tested on orogene desktop, took about the same amount of time. ok.
npm? 3x the amount of time (9 minutes!!), even though orogene web can only open two fetch requests at a time and has to serialize stuff between the Rust and JS layers.
lol. lmao. And orogene desktop was only a few seconds faster!
I should jump back on #orogene dev some time. This thing is still pretty solid.
#orogene web: 177.5s
orogene desktop: 157.861s
bun: 106.3s
npm: 540s
not bad for something done in someone's spare time, rather than with VC money, and that can run in the browser (!)
This is full cold start. No cache, no lockfile, nothing. Just a package.json and some vibes.
@zkat Curious, how does it compare to pnpm?
pnpm cold cache: 107s
pnpm warm cache + lockfile: 8.7s (??? not sure if I'm testing this right. This seems wrong.)
@zkat pnpm typically uses a system-wide package installation folder, so the second 'install' is likely just linking into that
@joepie91 I thought that would be the --store-dir, which I'm definitely wiping to test, but maybe there's more data being stored in the store dir about installations specific to certain projects in the system?...
@joepie91 it's complicated. These numbers would very likely be much closer on linux or macOS, too, which have... more reasonable file systems.