#T3 stack how to#
#T3 stack install#
#T3 stack full#
#T3 stack code#

Powered by the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor.Unlimited mode to ensure performance during peak periods.Burstable CPU, governed by CPU Credits, and consistent baseline performance.Custom built AWS Graviton2 Processor with 64-bit Arm Neoverse cores.Amazon RDS T4g instances are configured for Unlimited mode, which means they can burst beyond the baseline over a 24-hour window for an additional charge.

#T3 stack full#

Each earned CPU credit provides the T4g instance the opportunity to burst with the performance of a full CPU core for one minute when needed. T4g instances accumulate CPU credits when a workload is operating below baseline threshold. T4g instances offer a balance of compute, memory, and network resources and are ideal for database workloads with moderate CPU usage that experience temporary spikes in use. Since this is highly personal, I'll just go over this briefly.T4g instances are the next generation burstable general-purpose instance type that provide a baseline level of CPU performance with the ability to burst CPU usage at any time for as long as required. Below I'll just show a mockup usage of how this all works together! You can most likely skip this step, in that case you can skip to the final words. Before that, lets modify the router so we have something to display.Īt this point, your repo should look something like this. Your tRPC API is now setup and ready to be consumed. Force Metro to resolve (sub)dependencies only from the `nodeModulesPaths` = true module. Let Metro know where to resolve packages and in what order = // 3. Watch all files within the monorepo config.watchFolders = // 2. resolve (projectRoot, './.' ) // Create the default Metro config const config = getDefaultConfig (projectRoot) // Add the additional `cjs` extension to the resolver.

#T3 stack install#

Now, install all the dependencies using your preffered package manager:Ĭonst = require ( 'expo/metro-config' ) const path = require ( 'path' ) const projectRoot = _dirname const workspaceRoot = path. We'll use the tsconfig.json from the T3 app as base, and then inherit from this file in the T3 app: We'll also need a base tsconfig that we'll later inherit from. gitignore from your T3 app into the project root, and add.

Add the following configuration files into your project root, these are basic configuration files inspired by the turbo example apps: Now we'll install turbo and create some basic configuration files for it. Your repo should look something like this now. Move it into the apps/ sub-directory and scope-name it to something appropriate.Īlso clean out any temporary files, as well as your lockfile, we'll get all of those You'll see that it got named If you are using an existing app, just

#T3 stack code#

This uses Next-Auth.js which unfortunately doesn't supportĮxpo, but the code split can most likely be used with other auth providersĪt this point, you'll have a new T3 app in apps/nextjs, and if you check the package.json, The final repository that showcases how you'd code split that to work with the I'll break this process down into smaller pieces and commit accordingly, so that you can follow along as easy as possible. After that, we'll add an Expo app to the monorepo and consume the tRPC API on both web and mobile. TL DR, we are going to take an existing T3 app and split it into a monorepo using turborepo.

I'll admit the name might be deceiving since it isn't a scaffolding tool like create-t3-app is, but instead just a template repo with all the pieces included without any options to pick and choose.Īpologies in advance, this post is going to be a bit long, so for everyone who just want to see the final result, you can browse the repo directly here. I won't let y'all down entirely, so I decided to create a template repo that should help you setup a T3 monorepo. Then there's the new kid on the block, turborepo which we recently migrated the create-t3-app repo into so that we could have our upcoming documentation site in the same repo as the CLI scaffolding tool.īut. There are several tooling available for monorepos, including Lerna and NX.

#T3 stack how to#

We have turn these requests down due to the added complexity it would bring, and the fact that we do not want to prescribe how to run your monorepo. For a while now, we've been getting a lot of requests for including a CLI option to scaffold create-t3-app into a monorepo so that you can share code between your web and mobile application.