Clarification on defining tasks #9176
-
SummaryI'm looking at the guide for setting up Prisma: I'm wondering about the part where the tasks are defined: The database package has this script: {
"tasks": {
"dev": {
"dependsOn": ["^db:generate"],
"cache": false
},
"build": {
"dependsOn": ["^db:generate"],
"outputs": ["your-outputs-here"]
},
"db:generate": {
"cache": false
}
}
} I would have thought the "proper/clean" way to do this would be to just add a dev and a build script to the database package, like I've done in my other packages, and seen in many other examples:
If we had many packages, and each of them would choose a different name for their dev/build scripts, I guess this could quickly become a little chaotic and error prone. Of course both works, I'm just wondering if I'm missing something? Additional informationNo response ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You could choose to set up the tasks as you've described. The example is set up the way it is for simplicity, but is, of course, adjustable to your preferences. |
Beta Was this translation helpful? Give feedback.
You could choose to set up the tasks as you've described. The example is set up the way it is for simplicity, but is, of course, adjustable to your preferences.