Table of contents
Simplified Setup
React.run provides a streamlined and efficient setup for starting new React projects, minimizing the initial configuration time.
Pre-configured Environment
It comes with a pre-configured environment that includes essential tools and libraries, reducing the need for additional setup and compatibility checks.
Boost developer productivity
By automating much of the setup process, React.run allows developers to focus more on coding and less on configuring their development environment.
Consistency
Ensures a standardized environment across different projects, which can be particularly beneficial for teams and large-scale applications.
Community Support
Being an officially supported tool, it benefits from strong community support and timely updates from the React team.
Promote React.run. You can add any of these badges on your website.
Yes, React.run (react.dev) is a valuable resource for understanding and utilizing React effectively.
We have collected here some useful links to help you find out if React.run is good.
Check the traffic stats of React.run on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of React.run on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of React.run's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of React.run on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about React.run on Reddit. This can help you find out how popualr the product is and what people think about it.
Itโs already been captured. Check out the docs for creating a new React app on react.dev: https://react.dev/learn/creating-a-react-app It throws you straight at Next.js. - Source: Hacker News / 11 months ago
> The train of thought is โwhat is everyone using? Iโll use that tooโ I'm not so sure about that. We're seeing Next.js being pushed as the successor of create-react-app even in react.dev[1], which as a premise is kind of stupid. There is something definitely wrong going on. [1] https://react.dev/learn/creating-a-react-app. - Source: Hacker News / 11 months ago
The React documentation is infamously responsible of recommending Next as a "default". After a lot of backlash it got somewhat toned down, but it's still the first thing they suggest[1] for creating a new app [1] https://react.dev/learn/creating-a-react-app. - Source: Hacker News / 11 months ago
In times when the official React documentation says:. - Source: dev.to / 12 months ago
Vercel's playbook with Next so far has been to make convoluted features that exist solely to pad out how much people spend on hosting costs. They also make sure that hosting it anywhere but Vercel comes with footguns, even though theoretically you can host your Next app anywhere you want (and it's gotten better recently solely because of backlash). See https://opennext.js.org/ for example. They've been so... - Source: Hacker News / about 1 year ago
Luckily, the React team put up a list of possible CRA replacements as part of the deprecation announcement, and in this post I'm going to focus on the first option: Next.js. Why? IMO it offers the most features for going above and beyond just a simple migration. But we'll get into that later. - Source: dev.to / about 1 year ago
They exert immense influence over the React ecosystem, even its documentation. Example: https://react.dev/learn/creating-a-react-app If you are new to React and just figuring out how to get it running, you will likely end up on this page. The first recommendation is Next.js. The real best way for a beginner to start is IMO Vite. Comes with everything you need to get started and lets you choose what to do next.... - Source: Hacker News / about 1 year ago
[2] https://react.dev/learn/creating-a-react-app. - Source: Hacker News / over 1 year ago
> What do you get out of Next.js over vanilla React? The biggest problem is that React itself recommends against using Vanilla React. https://react.dev/learn/creating-a-react-app > If you want to build a new app or website with React, we recommend starting with a framework. This, frankly, is insane. The whole point of React was that it was this relatively lightweight UI library you could drop into pretty much any... - Source: Hacker News / over 1 year ago
I think people reasonably expect, say, an aws lambda to be aws specific. That's a very different story to React, which is supposed to be a library for general application ui development, and the official react documentation recommending Next as the way to use it. https://react.dev/learn/creating-a-react-app. - Source: Hacker News / over 1 year ago
Interestingly, the Creating a React App page (https://react.dev/learn/creating-a-react-app) does not mention Remix. - Source: Hacker News / over 1 year ago
The Getting Started docs recommend against using vanilla React and nudge you towards NextJS and similar frameworks because you're gonna end up needing that stuff eventually https://react.dev/learn/start-a-new-react-project So new projects have to actively not follow the recommended approach in the docs if they want to use vanilla React. - Source: Hacker News / over 1 year ago
I'm not saying I haven't seen it, but I would bet my lifesavings the overall percentage is quite small. Why is bringing up the minority use case helpful in these discussions? Some teams just use javascript and opt for zero dependencies, these teams are also an extreme minority. You can't have an earnest discussion about react if you're going to argue that no one pulls in a myriad of other dependencies. Even the... - Source: Hacker News / over 1 year ago
A common misconception. React is a library. These are examples for React frameworks: https://react.dev/learn/start-a-new-react-project#production-grade-react-frameworks. - Source: Hacker News / almost 2 years ago
The official React docs now instruct you to go straight to Next.js: https://react.dev/learn/start-a-new-react-project When React "is just a library" but the installation instructions tell you to install some large, VC-backed framework immediately - it just doesn't sit right with me. - Source: Hacker News / almost 2 years ago
Yea I'm not really buying it. create-react-app is deprecated. https://react.dev/learn/start-a-new-react-project points you directly at Next.js as a *starting point* and the section about using React without a framework does it's best to discourage you from doing it. This is insane for beginners. - Source: Hacker News / almost 2 years ago
The question I asked myself often is : Why did the React team bury the mention of Vite deep within a collapsed "Deep Dive" block on the Start a New Project page of their docs. Why does the mention of vite feel very brushed off, just a comment, a maybe not important note at the very end of a wall of text most people won't read? - Source: dev.to / almost 2 years ago
Here is the tricky situation and that's why CRA is in a semi-dead state, it has not been deprecated but isn't receiving any updates not even security updates, along with that the new React.dev documentation doesn't mention CRA but suggests using React meta-frameworks like Next and Remix for new projects. You can read more about React's reasoning for it in this github issue discussion. - Source: dev.to / about 2 years ago
The official React docs donโt share the same sentiment. They currently recommend the Pages Router and describe the App Router as a โBleeding-edge React Framework.โ. - Source: dev.to / about 2 years ago
The official react docs recommend using a meta framework for new projects: https://react.dev/learn/start-a-new-react-project This leads me to wonder, do they practice what they preach? If so what meta-framework do they use with react? Is it something in house? - Source: Hacker News / over 2 years ago
Https://react.dev/learn/start-a-new-react-project. - Source: Hacker News / over 2 years ago
Do you know an article comparing React.run to other products?
Suggest a link to a post with product alternatives.
Is React.run good? This is an informative page that will help you find out. Moreover, you can review and discuss React.run here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
