2 ms·
> It would be better, but it might also be borderline impossible or at least extremely difficult. Out of curiosity, what makes you say that? > What do you mea
by tentacleuno 5y ago
> It would be better, but it might also be borderline impossible or at least extremely difficult.
Out of curiosity, what makes you say that?
> What do you mean? This tool is not a package manager, it is just a script runner.
Bah, sorry. I had PNPM in mind when I wrote that (which I highly recommend). PNPM doesn't explicitly focus on startup time, but it does majorly improve performance as it caches packages.
- spion 5y agonode has a costly and intertwined init itself, where the startup cost is 50-100ms. On top of that, `npm` similarly has a high startup cost adding to the original node cost. Node apps are very slow to start to run due to synchronous `require` eager-loading all the module files, so there is some re-architecting necessary to get a performant startup time yarn v1 is probably the best of the bunch with startup lag close to pure node (100-150ms) yarn v2 and up can be extremely bad, 1s-3s with medium to large repos, especially with PnP enabled which AFAIK forces eager resolution. pnpm similarly has had troubles starting up quickly. It used to be even slower as it passed the command to `npm` in a suboptimal way. Nowadays its about the same speed as `npm` as it uses `npm` for `run`.
- deleted 5y ago[deleted]