What's the rational for not including the Packages directory?

[shammalie]

As the title mentions, when selecting turborepo with prisma and trpc using nextjs frontend and hono backend both apps use relative imports. But with turborepo or monorepo the common apporach for components to be shared across the project is to have them in the packages directory.

For example documenso is a good reference to an opensource monorepo and create-t3-turbo is great starter monorepo too.

What's are the reasons for not pursuing this approach?

[AmanVarshney01]

In the Better T stack, there are two main apps: web and server. Currently, the server only shares types with the web app. While having a separate package for shared types could be beneficial, it makes the most sense when logic is also shared between the apps. I’m not against placing a shared package in the packages directory, but the CLI’s default structure is designed this way for simplicity. Changing it would be a significant move due to the existing setup and dependencies.

[shammalie]

Hey, thanks for the response and it your approach makes sense.