Samuel on Warpcast

Content pfp

0 reply

0 recast

0 reaction

Samuel pfp

@samuellhuber.eth

Typescript backend/API what is THE go to? Hearing lots of nest.js next.js and tRPC talks. Also love what Adonis.JS is doing in bundling things you need anyways like lavarel. Just don't know THE one

12 replies

0 recast

3 reactions

Gabriel Ayuso pfp

@gabrielayuso.eth

for web app projects that don't need too much backend work building on NextJS is fine, especially if you want to ship something quickly and simple. If you want to push the envelope and not build yet-another-nextjs-app then don't use TS for backend, just for frontend (which can also be replace with a WASM lang).

0 reply

0 recast

2 reactions

andrew pfp

t3 (with tRPC) is IMO the smoothest out of the gate with data typing and validation https://create.t3.gg/ There are definitely limitations, but speed of execution and ease of deployment on Vercel makes it too easy

1 reply

0 recast

0 reaction

Joe Petrich 🟪 pfp

Joe Petrich 🟪

Don't? What's the impetus for using typescript?

1 reply

0 recast

0 reaction

max ⚡ pfp

Agree with @jpetrich, but if app is Next.js on Vercel no reason to not use API routes imo. Otherwise it’s about what makes sense for you/team. Ex: I only know modern JS/TS tooling and needed to go fast so working with tRPC on @nilli, etc.

1 reply

0 recast

1 reaction

sean pfp

i generally prefer other languages if i get the chance, but i gotta say the next.js ability to just create an /api directory to create endpoints (app router version) is shockingly simple. plus, just running it on vercel in only a few mins of setup (including a custom domain)- probably the best infra experience i've had

1 reply

0 recast

0 reaction

Steve pfp

@stevedylandev.eth

Might depend on your needs, but in my experience Next.js does just fine for less intensive tasks. It lets you build quick and dirty, then rewrite as necessary. More unified than anything else you’ll try out imo.

1 reply

0 recast

1 reaction

jtgi pfp

If you want typescript, I'd use next.js or remix.run with prisma. With Prisma you'll have a fully typed backend. I'm using remix.run lately, next.js with app dir and server components is a bit early and complicated (right now). I'd avoid nest unless you like Java and want to go slow. Its also only API side.

1 reply

0 recast

0 reaction

Mo pfp

Next.Js, it’s the five guys of web world Great value for money, fulfils all your requirements, sorts out front end and backend without much faffing around If back end only, koa (spiritual express successor) has worked great for me. Super lightweight and simple to use

1 reply

0 recast

0 reaction

christopher pfp

NextJS + NestJS is a good combination. NextJS isn’t ready for backend yet for anything production grade IMO

1 reply

0 recast

0 reaction

Darryl Yeo 🛠️ (at Devcon) pfp

Darryl Yeo 🛠️ (at Devcon)

SvelteKit + tRPC https://kit.svelte.dev

1 reply

0 recast

0 reaction

Mantej Rajpal 🇺🇸 pfp

Mantej Rajpal 🇺🇸

I’m also hearing lots of next.js

1 reply

0 recast

0 reaction

‍‍ pfp

https://hono.dev/ https://elysiajs.com/ https://nitro.unjs.io/

0 reply

0 recast

0 reaction