Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions turbo.json
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,16 @@
"outputs": ["dist/**", "build", ".svelte-kit", ".vercel/output"]
},
"dev": {
"dependsOn": ["^build"]
"dependsOn": ["^build"],
"cache": false
},
"typecheck": {
"dependsOn": ["^build"]
"dependsOn": ["^build"],
"cache": false
},
"test": {
"dependsOn": ["^build"]
"dependsOn": ["^build"],
"cache": false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me for test but not for dev since presumably we do want caching for dev, which is just a different kind of "build" step that also runs the code, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i assume that on dev we can't take full advantage of the cache because of constant updates, not fully sure though

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The build task would still be cacheable. But also frankly I don't think we even need a dev task. Does anybody use turbo run dev in this repo?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I use t dev for some things, but can just as easily use t build && p dev for the same

},
"clean": {
"cache": false
Expand Down
Loading