turborepo VS vercel

GitHub: vercel/turborepo

When you setup a monorepo using turbo, the basic template gives you 3 packages by default. This can be found in turborepo/examples/basic.

Next, let’s create monorepo with Turborepo.

> Look at the dependency tree for a next

Looks ok to me: https://npmgraph.js.org/?q=next

Ironically, most of the dependencies are actually Rust crates used by swc and turbopack [1]. Try running cargo tree on either of those crates, it's enlightening to say the least. And of course, Node has a built in file watcher, and even the most popular third party package for file watching (Chokidar) has a single dependency [3].

[1] https://github.com/vercel/turborepo/blob/main/Cargo.toml

[2] https://github.com/swc-project/swc/blob/main/Cargo.toml

[3] https://npmgraph.js.org/?q=chokidar

Turborepo: Smart build system for JavaScript/TypeScript monorepos

We’ve only scratched the surface of what we can do with Turborepo. You can find more examples in the Turborepo examples directory on GitHub. Skill Recordings on GitHub is also another great resource that has been around since Turborepo was first released.

git clone https://github.com/vercel/turborepo.git

I use https://turborepo.org/ to facilitate my monorepo. Essentially it's a way of structuring your configs, UI; apps etc and you consume each like an internal package. I find benefits for this as the kinds of sites I make will generally have an internal app, an admin panel and a marketing site. I can write UI, config etc in one place and consume them over the three projects to keep everything consistent.

The latest addition to the Composer Suite monorepo, Turborepo optimizes monorepo workflows by caching build artifacts. This may sound a little abstract and boring, but what this actually means is that when you build something within your monorepo, Turborepo will make sure only the things that it depends on are rebuilt; everything else will be retrieved from a cache that either lives on your local computer, or a remote cache server. Adding Turborepo to the Composer Suite monorepo pretty much halved CI build times, but it was also a way to teach Vercel, which I use for hosting the various example apps in the repo, to only actually deploy the ones that have changed since their last deployment. And that's really cool!

For a while, I had set up my DNS to proxy requests to Vercel's IP addresses. (See Github Issue #7739) But if you intend to use Cloudflare for edge computing, analytics or monitoring, then you might get the most benefit out of transferring your DNS to Cloudflare.

Frontend: Hosted on Vercel

Go to vercel.com & register if you don't have an account just yet.

Vercel

Sign up at vercel.com.

Building real-time apps in Next.js can be challenging. While the framework provides powerful full-stack primitives like API routes and server actions, it lacks native support for WebSockets. That’s likely because Vercel, the company behind Next.js, doesn’t yet support the WebSocket protocol on its platform.

This tutorial will show you how to deploy a simple Node.js (Express) app to Vercel. It’s perfect for beginners who want to get their API online fast — without worrying about infrastructure.

Before going to the Flutter code, publish this code to GitHub. Then open vercel.com, connect your repository, and deploy it.

2. Netlify/Vercel One-Click Deployment