3 ms·
> Fast connections and free bandwidth have caused people to completely ignore the fact that every time some CI pipeline runs, npm goes off and downloads 100MB o
by CharlieDigital 3y ago
> Fast connections and free bandwidth have caused people to completely ignore the fact that every time some CI pipeline runs, npm goes off and downloads 100MB of dependencies. Dependencies that haven't changed since the pipeline last ran 30 seconds ago.
Maybe it's just me, but I've always thought it was well known best practice to cache your deps[0].
I'm pretty certain that this can be achieved with most CI/CD tools.
https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows https://docs.github.com/en/actions/using-workflows/caching-d...
- justinsaccount 3y agoI've seen a lot of pipelines that simply don't bother. Or maybe they tried, but the caching isn't working and since the build works in the end no one notices an extra 30 seconds.