-
Hey everyone, My project structure looks like this
Previously, each of these packages had its own |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Not particularly a turbo specific problem, but you could create a root level config (or a package) for your base build config and extend that config in each package. (this is probably what I would do) Alternatively you could create a separate "scripts": {
"build": "custom-build --<any-custom-options>"
} With this approach turbo would require you to list this a |
Beta Was this translation helpful? Give feedback.
Not particularly a turbo specific problem, but you could create a root level config (or a package) for your base build config and extend that config in each package. (this is probably what I would do)
Alternatively you could create a separate
build-tools
package that builds a utility to programmatically run your build for the given package folder. So you could run something like this for each package:With this approach turbo would require you to list this a
dev-dependency
for each package so it knows to build that package first before everything else.