Skipping 'npm install' for a build agent that already has done that step

npm install creating node_modules (that itself is not under source control) is a time consuming step.

What is the best practice for retaining a node_modules directory between build-kite builds for a build agent that already done the work?

Hey @paul_h!

We are working on a cache plugin that will address these types of situations, but in the meantime, something you can do is to have a step that does the installation and create an artifact with all the dependencies, and download it on the rest of the steps.