As I have explained in another post: https://community.vercel.com/t/looking-for-feedback-on-structuring-a-big-project-with-turbo-repo/6279

Vercel Community

Looking for feedback on structuring a big project with turbo repo

We’ve been using Turbo Repo for over a year and would like feedback on our app/package structure and setup: Current Structure: /apps/web-1...

The way we decided to implement the repository, using nested packages with pnpm workspaces, doesn't seem to be working as I expected.

We are in the process of migrating from react-router v6 to v7, and scaling this app to the setup we have, it's getting chaotic.

Short summary of our setup

1
/ ← repo root
2
├── package.json              # “my-monorepo” 
3
├── pnpm-workspace.yaml       # includes apps/**/* , shared/**/*
4
├── turbo.json                # defines pipeline (build, dev, test, etc.)
5
├── apps
6
│   └── web-app 1
7
│       ├── package.json      # “@web-1/root”
8
│       ├── src/
9
│       └── packages/         # nested workspaces
10
│           ├── ui-kit
11
│           │   └── package.json  # “@web-1/ui-kit”
12
│           └── utils
13
│               └── package.json  # “@web-1/utils”
14
│   └── web-app 2
15
│       ├── package.json      # “@web-2/root”
16
│       ├── src/
17
│       └── packages/         # nested workspaces
18
│           ├── ui-kit
19
│           │   └── package.json  # “@web-2/ui-kit”
20
│           └── utils
21
│               └── package.json  # “@web-2/utils”
22
│
23
├── shared (across all apps)
24
│   ├── config
25
│   │   └── package.json      # “@shared/config”
26
│   └── hooks
27
│       └── package.json      # “@shared/hook”

All the dedicated web-1 and web-2 packages are JIT, sort of packages, meaning that they are all dependent on the corresponding app.

Questions, where I would like to get feedback:

• Because we use JIT, does this mean we have to define the exports explicitly?
• If I use react-router in web-1, do I need to install that dependency on every nested package if I want to use anything from it? Or is it better to use peer dependencies in this case?
• Are the names we pick for the packages ok, or do we have to follow a particular pattern for them to work?
• What would be the best approach for installing a new dependency? I have tried the following, but it doesn't seem to follow the dependency tree: pnpm add react-router@latest --save-dev --recursive --filter=@web-1/root.
• If there are other packages under "shared" using react-router as well, should that be different?
• When I try to make a dependency chart, it seems like we have circular dependencies, but in practice, we don't. What could I be missing?
• Offtopic, but still related, is there any specific AI model recommended to work with turborepo? No matter how much I try to specify rules or instructions, it never generates decent outputs.

To be honest, even though it's not discouraged, having nested packages it's the root of our issues.

Sorry for the long post! Thanks again!