Each React framework has a community, so finding answers to questions and upgrading tooling is easier.

They let you start very lean and then scale your app with your needs. React frameworks on this page solve problems like these by default, with no extra work from your side. Building these capabilities yourself takes real work. You may want to generate a folder of fully static HTML files for your marketing pages that can be hosted anywhere and still work with JavaScript disabled. You’ll likely want the page to be interactive before your JavaScript code even runs, to support progressive enhancement. You’ll want to send down the minimal amount of app code but do so in a single client–server roundtrip, in parallel with any data required for the page. It’s not hard to get an initial setup working, but there are a lot of subtleties involved in making an app that loads quickly even as it grows over time. To solve these problems on your own, you’ll need to integrate your bundler with your router and with your data fetching library. This is why Svelte has SvelteKit, Vue has Nuxt, and so on. Changing your setup to run some of your code on the server or during the build can be very tricky.

As your audience includes more users with poor network conditions and low-end devices, you might need to generate HTML from your components to display content early-either on the server, or during the build time. As your data fetching needs get more complex, you are likely to encounter server-client network waterfalls that make your app feel very slow. As your JavaScript bundle grows with every new feature, you might have to figure out how to split code for every route individually. However, if you’re building a new app or a site fully with React, we recommend using a framework.Įven if you don’t need routing or data fetching at first, you’ll likely want to add some libraries for them. You can definitely use React without a framework-that’s how you’d use React for a part of your page.

Npm react