-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix circleci caching paths #513
Comments
While I'm working on this, should we remove yarn.lock files from the cache? I added them because there was a |
|
They are cached by the circle ci caching layer, so they are created and persisted between multiple test runs until the cache breaks (by changing a package.json file). |
Oh got it, for me which should either use them at every step (so commit them inside the repo) or not using them at all |
I would argue for not using them at all. We want to make sure we get the versions of dependencies that our end users will get. It is up to them to lock their dependencies. |
@dyladan Can we close this one? |
* chore: update core to 0.20.0 * chore: fix test * chore: review comments and lint * chore: get example versions from previous update * chore: lint
* chore: update core to 0.20.0 * chore: fix test * chore: review comments and lint * chore: get example versions from previous update * chore: lint
Is your feature request related to a problem? Please describe.
Circle CI caching paths include a
*
glob. According to the docs, globbing is not allowed in the paths array.Describe the solution you'd like
Each package node module directory should be manually added to the globs array.
Please assign to me. PR incoming.
The text was updated successfully, but these errors were encountered: