create-t3-app

I agree that the quantity of publicly available code isn't the most reliable indicator of someone's seniority. My issue with this individual arises from the discrepancy between his public claims of significant expertise in the content he produces. He positions himself as a highly experienced developer, attracting a large following of junior developers who take his advice at face value. I am trying to collect data points supporting his claims of seniority. For instance, his website prominently features a statement that he is the creator of the T3 Stack. However, a review of the contributor statistics for the T3 Stack https://github.com/t3-oss/create-t3-app/graphs/contributors reveals minimal contributions from him, which raises questions about the validity of his claims.

https://github.com/t3-oss/create-t3-app You still would need to add Stripe but there are so many examples publicly available that it should be straight forward

https://github.com/t3-oss/create-t3-app hosted on Vercel + Planetscale / Railway DB is very easy, I would be surprised if you were miserable doing that. Mostly that solves setting up Auth and Prisma SQL ORM to your DB, but Next.js App directory with the Prisma setup (2 files / 50 LOC) done is even smoother.

create-t3-app is a great starting point for folks going this path. Has optional checkboxes for db/ORM/migrations (prisma.js), auth/sessions (next-auth.js), tailwind CSS, typed client/server communication (trpc). https://create.t3.gg/ https://github.com/t3-oss/create-t3-app I hadn't touched much webdev for a few years, the ecosystem / build tooling has gotten a LOT better. It's back to being fun and painless to spin up a new webapp.

T3 stack: https://create.t3.gg/ https://github.com/t3-oss/create-t3-app It's Next.js, Typescript, TailwindCSS, Prisma, NextAuth, tRPC. > I know about Node.JS, Angular, React, Express You already know just JS. Stick with JS framework, not these Rails suggestions. Next.js is by far the biggest JS framework (ChatGPT page? half the recent YC co's? Next.js), the rest are the niceties around it to get to a full solution. > A central definition of data schemas. I don't want to define my schema or validation twice, once in the frontend and once in the backend. T3 stack uses Prisma, a JS/TS "ORM". Your data schema will live in a .prisma file. > Automatic generation of REST endpoints. I hate boilerplate code and don't want to reimplement Get/GetOne/Add/Update/Delete and Websocket for each data model. Even better would be a GraphQL interface. Includ

Look into T3 stack [0] and maybe Remix - if you know Node.js it will make things easier for you IMO. [0] https://github.com/t3-oss/create-t3-app

Interesting take, the article describes ENV variables and their inherent untyped danger when you depend on them, but doesn't really describe an alternative solution for them. A good solution I've just seen is to validate the environment variables using a schema like [1] zod. Which will guarantee that the ENV variables are the exact type that you expect when the program starts, or it will throw an error. [1] Example -> https://github.com/t3-oss/create-t3-app/blob/bc57d02789209f1...

Create T3 app https://github.com/t3-oss/create-t3-app I was fairly new to "modern" web dev, starting a project, and went with Django because I had more Python experience than anything else. But I found templates very lackluster and poor to integrate with all the different JS ecosystem libraries people are creating to do very cool things on the frontend. Unfortunately, hooking React up to Django is a mess and most people doing this are still 5 years behind in React-land. Are you going to hybrid some template and some React? Are you going to containerize your django and react build system together? Basically, I wanted a robust frontend ecosystem, well integrated to a simple backend (no Spring, Django-Rest-Framework monstrosities). That led to React -> Next.js -> Typescript backend -> the rest of the niceties around it like Prisma (ORM-ish)

Getting Next.js up to Rails feature-wise is using something that already wires up the niceties like Auth, ORM, Tailwind styles, and Typescript. Create-t3-app is a huge contender here: https://init.tips/ and https://github.com/t3-oss/create-t3-app A DB is as simple as pressing a button on Planetscale or Railway, copying the secret strings to your .env file, and 'npx prisma db push'.

https://github.com/t3-oss/create-t3-app + Pnpm monorepo

To throw another in the ring, I recently stumbled on https://github.com/t3-oss/create-t3-app. Lots of buzzword tech in there, but the setup looks very interesting. Looks like blitz is tRPC + next auth?

- SSR vs client side: NextJs does this automatically. https://nextjs.org/docs/basic-features/pages - GQL: the only case where I'd use GQL is where he would likely want to too: building native mobile apps. Otherwise, I'd use tRPC and have fullstack type safety. This is included in my 5 minute estimate because I'd use create t3 app, which has this configured out of the box https://trpc.io/ https://github.com/t3-oss/create-t3-app - monitoring/observability: not quite sure what you mean, but it's only a few clicks in vercel to have a logdrain or metric drain and configure alerts and dashboards in your tool of choice. And if I wanted to roll the whole thing myself... that's what he did. Rolled it all custom by hand. The difference is I have the option of not reinventing the wheel. At the end of the day I can get into composing a docker image

Extend the User model in Prisma: https://github.com/t3-oss/create-t3-app/blob/main/cli/templa... Here's the file you add auth "providers": https://github.com/t3-oss/create-t3-app/blob/main/cli/templa... Custom providers: https://next-auth.js.org/configuration/providers/oauth#using...

I was similar; an embedded C++ engineer moving into web dev to get a project off the ground. If you're going to write a modern web frontend like Next and Tailwind (which I agree is the right call) then I think continuing to use Typescript for your backend makes sense for sheer development velocity. Like https://github.com/t3-oss/create-t3-app I'd advise against Heroku compared to hosts like Vercel, Railway, Planetscale, etc.

What do you mean? There's so many Heroku competitors these days that the perception has changed towards Heroku being a relic of "how it used to be done". Competitors like Vercel don't just do what Heroku does, they do everything better. (And now edge-first ideas like fly.io are catching on) Another start-up I've been playing with is Railway, who offers 5-10$ of free usage per month, certainly enough to play with react/nextjs app and a postgres db to your hobbyists hearts content (as long as you turn if off when you're done). If I were to host a bootcamp on starting a web app from scratch I'd do something like stand-up a T3 App https://github.com/t3-oss/create-t3-app on Vercel Hobby https://www.vercel.com . Not sure I'd even consider Heroku for teaching anymore.