upvote
This is like saying a Java library readme should start with what the JVM is. It's fine to not know these things, but the majority of this comes with the territory. Right now it sounds like you're simply not the target audience. The Github readme includes a link to all of the major bits, so I don't really see the problem.
reply
If you were trying to convince me to build a web app in Java, you wouldn’t need to explain what the JVM is, but you’d need to make a strong argument for why Java is better than the alternatives available in 2025.

So the question is whether the target audience here is “people who want to build full-stack web apps” or “people who are already using the BHVR stack”.

reply
The benefits are very clear to me.

If you build MERN apps, this is a template that replaces Express with Hono, Node with bun, and Webpack with Vite.

All of which are significantly faster than their counterparts. Hono can be deployed anywhere and has a much smaller bundle size than Express.

reply
These two paragraphs would already be a much more helpful project description than “typesafe fullstack monorepo”.
reply
If you've never heard of Bun or Vite you're clearly not the audience for this.
reply
Why not? There are a lot of people who use the 2010s de facto standard JS server stack — Node, Express, Webpack etc. — but don't necessarily have the time or inclination to keep up to date with every new project in this space. It's a lot to follow.

The exclusive gatekeeping messaging doesn't seem very useful. There's probably a much bigger audience for "Hey, instead of starting yet another Node project, why not try this?" rather than preaching to the already converted early adopters.

reply
Vite is a project with 25M weekly NPM downloads and used by some 9M github repos. It's not an obscure project by any stretch of the imagination. Heck it's almost as popular as React.

https://npmtrends.com/react-vs-vite-vs-webpack

Imagine someone posting a project that uses React and then someone demanding they explain what React is...

reply
You are selecting the frontend crew and making claims based on that. Many of us are not frontend devs just want to wrap an API. At least I do.
reply
> Many of us are not frontend devs

That's fine but OP's template is clearly for devs with frontend skills. No?

reply
Heard not an expert in, parent is right
reply