Migrate to Turborepo
in progress
Support
The next big step in the boilerplate is to use a monorepo like turborepo to manage multiple application domains.
Example structure
/apps
/api - public API
/app - web app
/web - marketing, blog
= multiple instances. For the public API I'm still debating what framework, likely Nest.js or Hono.js.
/packages
/config
/db
/emails
/types
/ui
= everything that can be shared between apps.
Anton Stasyuk
Any news on this one?
Support
Anton Stasyuk Hi, the work on this is still going on.
The slowdown was because of the multi-organization support which is now in the test phase: https://demo-v2.achromatic.dev
(PR: https://github.com/achromaticlabs/pro/pull/39)
Turborepo will be released together with multi-org as v2 of the boilerplate since both are substantial and/or breaking changes.
P
Phat Tran
Hi Support
When do we plan to finish this? Have we decided on the BE framework?
Daniel Skov Jacobsen
NestJS is better choice for API than Hono.js. Hono.js is great and I love building with it, but if you want to use Hono.js then you can easily opt-in to that on Next.js API routes and even host them on Cloudflare.
Choosing NestJS will enable building truly enterprise grade projects in a microservice architecture with API-Gateway, Shared / common packages, queues systems with RabbitMQ (or other) etc.
NestJS is not slow at all - not if you build it right and you can easily replace Express framework with Fastify (or even Deno 2.0) to gain even more performance. Another aspects for choosing NestJS is also the rich ecosytstem of express (npm packages).
NestJS is also not cumbersome to host. It's straitforward and easy. Of course you dont deploy NestJS on Vercel, but the whole point of separating this in monorepo architecture with Turborepo is to enable enterprise grade applications, else you can just as well build your Next.js API with Hono.js already.
C
Codebird
When is the Turborepo going to be released? Also, kindly consider Hono for APIs.
L
Leonardo Marciano
NestJS is cumbersome to host and somewhat slow nowadays due to its dependency on Node. Hono, on the other hand, is more modern and barrier-free, making it possible to use Bun, which delivers incredible performance results.
Bun + Vine.js (Vine is much more performant than Zod).
Another option is Encore.ts. Despite being new, it allows hosting on your own infrastructure, enabling developers to avoid managing databases, API gateways, firewalls, object storage, and notifications across multiple clouds. It offers a well-configured (and secure) deployment, unlike the trend of VPS platforms gaining popularity on Twitter that disregard distribution, resilience, and other critical aspects.
By far, it’s the best option, as Encore’s runtime outperforms even Bun’s runtime.
It’s also open-source.
The only issue is its current lack of popularity.
Anton Stasyuk
I think it’s a good idea to keep the UI for the CRM (admin panel) separate from the rest of the app. Instead, I'd focus on extracting the common helpers and hooks that can be used across different platforms. In real-world scenarios, it’s rare to have the same style for front-end as for internal systems. Also, Shadcn is primarily designed for building dashboard-like UI.
Basil T
Anton Stasyuk Agree with this aswell
Support
in progress