turborepo VS Express

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!

Node.js with Express (https://expressjs.com/)

So that’s the first big downside of building a REST API without using packages like express.js - you have to build all the route handling yourself, plus add some support for middlewares.

Express.js Documentation

Express.js was created around the time callbacks were _the_ architecture in Node.js. The world, including UI, quickly found callbacks do not compose well, and void return values are hard to test because of side-effects. Promises were created so you could compose functions, but still have control where your side-effects go. This negates the need for middlewares / callbacks.

The Devvit team just announced a new experimental way to build WebView based apps for Reddit. Previously only static HTML/JS/CSS could be used. With this new version, it is possible to run server-side code through Node including spinning up an Express server.

Basic knowledge of JavaScript and Express

With that set, we can import callOpenAI on a controller. I am using express to manage the API endpoint.

The basis of my small API proxy is the NPM package http-proxy-middleware from Steven Chim, which I utilized to build a system that can be used via configuration for various endpoints and that runs on a server under the Node.js framework Express.

Fiber: Go framework inspired in express.

These packages are not limited to Lambda. You can use them to validate tokens in Express servers running on EC2 instances or containers, for example.