Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Steve
@stevedylandev.eth
You can just make a new stack ¯\_(ツ)_/¯ Introducing bhvr 🦫 Bun + Hono + Vite + React Fully typesafe monorepo starter check it out with bun create bhvr bhvr.dev
24 replies
27 recasts
101 reactions
artlu 🎩
@artlu
so nice 👍 I just made my own cf + hono + vite + preact starter last week! this beaver 🦫 is tempting!! btw have you tried hono/client ? no shared types needed, just change the backend and the frontend knows
1 reply
0 recast
3 reactions
Steve
@stevedylandev.eth
Ty!! 🙏🏻🙏🏻 I’ve messed around a little bit with hono/client but stuck with vite since there’s so many ecosystem plugins for it, e.g. tailwindcss, shadcn, etc
1 reply
0 recast
3 reactions
artlu 🎩
@artlu
it can be orthogonal, I believe, purely as dx. I use hono/client while creating static react via vite. in my editor, I get strict type safety (nameless shapes), with auto-complete and no code-gen or file watching to slow things down. Front and back remain isolated, but tied together in the editor
1 reply
0 recast
1 reaction
Steve
@stevedylandev.eth
Hmm, gonna have to take another look at that 👀
1 reply
0 recast
1 reaction
artlu 🎩
@artlu
am hooked on bhvr, got me playing with my bhvr-cfnk out in public! this commit replaces the shared package, with hono/client inferred typing. you can change the backend return shape, and typing on the front-end catches it right away. there's a bit of intimidating-looking Typescript on the front end; can be mostly avoided if you run the client and server in the same repo and use hono's fetcher. But the flexibility to deploy separately is worth keeping imo. https://github.com/artlu99/bhvr-cfnk/commit/6e57ddd7577da884ec1a4434d9ca960f86e50dbe
1 reply
0 recast
1 reaction
Steve
@stevedylandev.eth
Sick!! Yeah I was exploring the hono/client package a bit this weekend. I'm still on the fence of whether or not to use it as a default. The one issue I've read is that using the RPC can really bog down your editor depending how large the project gets. As with any template I kinda prefer to keep it barebones as much as possible so people can edit and add to it as they please. It's much easier to add something than to remove it in my experience.
1 reply
0 recast
1 reaction
artlu 🎩
@artlu
yes, quite easy to add, hard to change later lol I'm eager to deploy the two pieces separately, and see how little/much work is required to keep them in sync as compared with a single deployment. good heads up on bogging down the editor. I'll try to push the envelope to see how soon that happens
0 reply
0 recast
1 reaction
