Is your feature request related to a problem? Please describe.
When running the frontend CI GitHub actions, the node modules are installed every job from scratch (for the linting step. For the cypress step the node modules are already cached.).
Describe the solution you'd like
The newer versions of the setup-node action incorporate dependency caching. We should do some research on this and likely upgrade to setup-node v5 or v6.
Describe alternatives you've considered
We considered using a separate GitHub action that specifically handles caching but discovered that this functionality is built into setup-node newer versions.
Is your feature request related to a problem? Please describe.
When running the frontend CI GitHub actions, the node modules are installed every job from scratch (for the linting step. For the cypress step the node modules are already cached.).
Describe the solution you'd like
The newer versions of the setup-node action incorporate dependency caching. We should do some research on this and likely upgrade to setup-node v5 or v6.
Describe alternatives you've considered
We considered using a separate GitHub action that specifically handles caching but discovered that this functionality is built into setup-node newer versions.