alt Hacker NewsShow HN: Bhvr, a Bun and Hono and Vite and React Starter
Hey all! I've been using this stack personally for a while now and decided to automate it a bit by turning it into a template I can reuse. Hope others might find it helpful!
Comments
Hono also has an official Vite devserver plugin if want an easy way to run a single integrated dev server locally for an API which also serves up your UI and has the hot reloading goodness you want.
I've used a very similar setup for a couple of new projects which were about to default to Next.js but didn't really specifically need what Next.js does (e.g. its SSR abstractions, these were internal, client-only apps sitting behind an auth redirect) from wasting their time fighting it.
Hono also supports JSX on the backend out of the box of you want to use components as a superior alternative to string templating libraries to serve up some HTML, a middle ground of sorts if Astro (:heart:) is too much for what your app needs to do.
I haven't needed to take advantage of this yet, but if you don't need full-fat React, it can also SSR and run on the client, sort of "vanilla JSX" if you will (sorry).
Hono is great. It's a shame it all depends on a single maintainer and there's zero official funding afaik.
Nice! I built something similar yesterday. But decided to use elysia instead. They have a tRPC like client with full TS support called eden.
Using Hono RPC would immensely help this. I'm using a similar kind of setup for my upcoming micro SaaS and the API integration has been a breeze
I never use templates because it’s much faster to create a new project from scratch than use a template and remove all the unnecessary things.
Alternatives are good, but there is almost no information on this site. I went to the site hoping to see things like what a route looks like, the syntax, how I might create a page or layout, how to make server only things vs. client only things, etc. None of that is on the page or GitHub README though. Not even one code example. Show people how this works!
Is there a stack for loading html safely from the backend that has proper error handling? I would love to use HTMX but not sure how to do (for starting) error handling in it. I need to render some backend generated charts mostly, maybe adjust the time (datepicker). Is there something for this or just use vanilla?
I'd love a stack that was
- NestJS - React Router - React
Whatever bundler/pack-man you want to use, go ahead. I'm curious which one would objectively be better, because I'd go for vite due to familiarity
I really want this, but BHVS, where react is replaced with svelte.
Thanks, I really hate Remix and especially NextJS. But what about LTS? What is there are no updates after 6 months?
Also, does this have SSR?
I think it's wonderful that there's a choice to use whatever package manager you like for your own personal work. But there is a special place for anyone who uses anything other than npm with a stable Node LTS for a professional project that will need to be maintained.
the main benefit of hono seems to be you can deploy to cloudflare either as a pages app or workers. so this is kind of like a 'sveltekit for react'.
in which case it would be nice to see it extended slightly: tailwind client side and eg drizzle ORM - basically the minimum you need to really ship a client/server app
Just a heads up, the repo description says "vice" instead of "vite"
Would it make sense to ReactRouter SSR though Hono?
If not, great opportunity for bvrrr.
Why bother with Vite if you're using Bun? Also, Hono is nice but I personally I prefer Elysia in that ecosystem. Anyway, thanks for sharing!
This is awesome! Why bun over deno? Curious your decision making process there. Making a similar but opposite decision there.
I just switched to hono.js. I like it.
Needs an example project IMHO.
great work and very neat repo, love it!
Do you have a plans to add the ORM?
Thanks for this, a few Qs though
1. How does this compare to the MUNGG stack?
2. When can we expect compatibility with Curlew templates?
3. I get cryptic build errors when I add Seieki.js as a dependency. Has anybody else experienced this?
I think you might want to elaborate on why this stack is good.
Right now it’s summarized as “typesafe fullstack monorepo”… But that’s so dense, it’s practically just three buzzwords together. A more realistic description of the pros and cons would be welcome.
I’ve never heard of Hono, and I’d personally need a lot more convincing to pick an unknown framework for a new app.