-
|
Recently I was tasked to spinup a turborepo, called monorepo/
├─ backend/
│ ├─ api/
├─ turborepo-frontend/
│ ├─ apps/
│ ├─ packages/
│ ├─ package.json
│ ├─ turbo.json
├─ infrastructure/
│ ├─ aws/
│ ├─ Pulumi.yaml
├─ .gitignore
├─ README.mdI honestly am not sure how to proceed. Do I need to add a |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
This answer is pretty late, but if you're still looking for an answer... the easiest path is probably to move your |
Beta Was this translation helpful? Give feedback.
-
|
No worries about the late reply. Yep, this is how we proceeded. It has grown significantly since Mar 2022. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for coming back here and replying! Just to be clear, which did you do? |
Beta Was this translation helpful? Give feedback.
-
|
turbo config to root |
Beta Was this translation helpful? Give feedback.
This answer is pretty late, but if you're still looking for an answer... the easiest path is probably to move your
turbo.jsonto the root of the repo. Alternatively, in Turbo 1.7, we introduced the ability to installturboglobally on your system. With that, you should be able to leaveturbo.jsonwhere it is andcd turborepo-frontend && turbo run build. (I haven't tried this, but I think it should work).