Steve on Warpcast

Content pfp

https://opensea.io/collection/dev-21

0 reply

0 recast

2 reactions

Stephan pfp

if i'm coming from nextjs, what is the closest vite-based monorepo setup that lets me do frontend + backend api development? everyone keeps shilling vite to nextjs users but i've never found a good answer for this

19 replies

2 recasts

23 reactions

dylan pfp

been wondering this as well, cc @stevedylandev.eth @samuellhuber.eth any recs?

3 replies

0 recast

5 reactions

Steve pfp

@stevedylandev.eth

I personally would highly recommend Vite React + Hono.dev, it’s such a good experience. With this approach you can easily deploy either one in multiple places making them very portable. I tend to like keeping the repos separate but this might nerd snipe me into making a monorepo template 😭

1 reply

0 recast

5 reactions

Stephan pfp

i've heard this many times and would love to try it but i want my backend and frontend in the same repo. do you know of a template or create next-app equivalent?

1 reply

0 recast

2 reactions

Steve pfp

@stevedylandev.eth

Not that I’m aware of, which is kinda why I might try to make one. Question though: when you say “same repo” does that mean you’re cool with two subfolders “server” and “client”? Or are you looking for something that is all SSR?

1 reply

0 recast

2 reactions

Stephan pfp

don't care about ssr most of the time client side compute is underutilized imo :p

1 reply

0 recast

2 reactions

dylan pfp

+1 I just care about the monorepo/shared code aspect here(agree on the client side note too although there’s a place and time for ssr)

2 replies

0 recast

1 reaction

Steve pfp

@stevedylandev.eth

So big want is like shared packages and types correct?

1 reply

0 recast

1 reaction

dylan pfp

from my POV yeah that would be awesome/helpful & is the mental model I think of when I’m traditionally using JS monorepos

1 reply

0 recast

1 reaction

Steve pfp

@stevedylandev.eth

1 reply

0 recast

0 reaction

Samuel ツ pfp

@samuellhuber.eth

you can get that as steve mentioned anywhere by sharing schemas/types but full stack framework wise it's react router 7 (prev remix) otherwise frontend + api in one repo just comes down to making sure deployment works for both watch out for what @rafi is cooking with effect bundler. (I assume I can put effectHTTPApi in there for backend)

1 reply

0 recast

1 reaction