Turbo caching dependencies
#10827
Replies: 3 comments
-
|
If I make a change in that package it seems to hit 13 workspaces with |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Could it potentially be related to PNPM's |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Seems like it just needed a dependsOn: ["^test"] |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Let's say we have an app, that's dependent on a package. If the package changes, turbo will recognise that there has been changes, so it won't hit the cache & execute the test command for the package. However, it seems that for the app the test command hits cache & has been skipped, even though some stuff in the app might have changed due to the package changes
Do we have something wrongly configured, expected or a bug in turborepo?
Additional information
{ "$schema": "./node_modules/turbo/schema.json", "ui": "tui", "tasks": { "build": { "cache": false, "outputs": [ "dist/**", ".next/**", "!.next/cache/**" ], "env": [ "NODE_ENV" ] }, "test": { "cache": true, "outputs": [ "coverage/**" ] } } }Example
No response
Beta Was this translation helpful? Give feedback.
All reactions