Post

react.dev is designed for folks who are new to React or are learning basic React concepts. While we'd love to have docs for more advanced users of React (e.g. libraries, frameworks, build tools, etc.) we don't have the resources to make that happen today.

Because react.dev's audience is new users, the recommendations are also tailored to new users. We don't want to recommend a path for new user where they may have to rewrite a significant part of their app to get a feture they figure out they need down the line

Its hard to recommend a build tool to someone new to React knowing that they might find themselves needing a different rendering strategy (e.g. CSR, SSG, SSR) per route, with data fetching included

We think there is a place to recommend Vite and that is why we created the "Build a React app from Scratch" page. We wanted to have a place to recommend build tools without leading new React users down a path we can't, in good faith, recommend react.dev/learn/build-...

This isn't perfect and most of the folks reading this post aren't the primary audience for this page (or react.dev) because they know the tradeoffs already and can make their own, informed decision.

Won't the people in the intended audience (who are not informed to make their own decisions), simply ask a LLM to build their app, nowadays?

Stack overflow questions and an endless maze of procedurally generated sitemaps 🔥 Wait, are you telling me the 𝑎𝑐𝑡𝑢𝑎𝑙 audience of react.dev is LLMs? 🙃

I never really got the "let's just hide the complexity to avoid confusing the audience" argument. These new devs end up battling reduced portability due to runtime constraints from the framework, jargon overload and overall complexity, just because they might need some feature in the future? 🤷‍♂️

If React is true to its promise of composability, it shouldn't be a total re-write to "upgrade" to using a framework, right?