craco
rfcs
craco | rfcs | |
---|---|---|
32 | 98 | |
7,368 | 5,399 | |
0.3% | 0.7% | |
6.4 | 2.9 | |
4 months ago | 4 months ago | |
TypeScript | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
craco
-
Htmx and Web Components: A Perfect Match
I had some 'fun' figuring out how to deal with not going through create-react-app without doing a full eject, got something barely working ... and discovered https://craco.js.org/ already existed and did precisely what I'd part-implemented except better.
On the upside, by that point I knew the CRA codebase well enough to predict what it would do even in edge cases, and CRACO's implementation was immediately comprehensible, and none of my colleagues had to try and understand my half-arsed NIH version.
(avoiding being in any of this situation in the first place would likely have been preferable, but given where things were when I landed on the project in question that would've required a TARDIS)
-
Gzip Compression and IIS Setup on Windows Server for React Projects
If you initiated your React application using create-react-app, leverage @craco/craco to override your webpack configuration.
-
Build a web editor with react-monaco-editor
Ejecting a React app is a bad idea because our application will lose all the React configurations and will not benefit from the CRA updates. Some solutions for ejecting our application include using packages like react-app-rewired or rewire. You can also use CRACO to eject your React application, but it needs you to install additional plugins.
-
How are you building React applications? It's time to move on from Create React App
So, instead of entirely managing these configuration files, teams took to utilizing tools such as Craco to override configurations. These tools also come with their limitations: they were not updated as quickly as CRA, so there was always a lag in implementing new features, and they added an extra layer of complexity to existing tools through overrides and additional tools.
-
How to start a React Project in 2023
I am not much of a fan of CRA myself but I am very much glad that https://craco.js.org exists - so far it's handled my needs for tweaking CRA behaviour in situations where "eject" didn't seem like a good route to take.
Mostly tbh to stop the freaking thing spawning inotify watchers for the entire contents of node_modules - I don't mind having to do a manual restart when I've changed dependencies and I definitely -do- mind having it eat a shedload of my user's inotify kernel allocation. (I know you can up the allocation, that's not the point, why are you on my lawn? :)
- How can I make my CRA server start up quicker?
-
How to bypass mobile app review thanks to Capacitor, Ionic, and micro frontends 🤯
As I mentioned, in our case, the perfect tool for this job is CRACO. It will let us simply overwrite CRA’s configuration without ejecting.
-
Top packages for React Development
Create react app + Craco
-
Working with Ant Design in React - Customization
Or I could use Craco with Craco-less. Craco 6+ doesn't work with 5+ versions of react-scripts. I know I could use yarn instead of NPM which doesn't stop the installation of craco, but it can't be the solution. We can't scrap the project and restart. Further, Craco 7-alpha installs but then craco-less doesn't.
-
CRA vs Parcel
If you want to customize the webpack configuration, you either need to eject, or to work against the package (with yarn patch, forking react-scripts, or using CRACO which is the easiest). But none of them are officially maintained by the CRA team.
rfcs
-
React Labs: What We've Been Working On – February 2024 – React Compiler
Examples from the conversations of that time:
> ...we want closures to capture the values we rendered with, and to keep "seeing" those values forever. That's really important for concurrent mode where a notion of current value doesn't really exist. Hooks design models a component as being in many non-clashing states at the same time, instead of switching the "current" state (which is what classes model well). People don't really need to think about these details, but they're motivating the design a lot. [0]
> In Concurrent Mode, render may run more then one time, and since this in a class is mutable, renders that should be the same may not be. [1]
[0] - https://github.com/reactjs/rfcs/pull/68#issuecomment-4778866...
[1] - https://tkplaceholder.io/why-function-components-fit-react-b...
- A modest request: How do you fetch data in React 18+ WITHOUT a third party dependency?
-
Optimizing performance: how our extension became lightning fast
There are multiple names for this hook. You can find the documentation under the names useEvent or useEffectEvent.
-
The Sisyphean Quest for Web Performance
-https://www.patterns.dev/ -https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md -https://dev.to/this-is-learning/qwik-the-post-modern-framework-3c5o -https://dev.to/this-is-learning/astro-framework-169m -https://developers.google.com/web/updates/2019/02/rendering-on-the-web -https://web.dev/vitals/
- Why Do I Need RSC(react server components) if I Already Have Remix
-
Declaring JSX types in TypeScript 5.1
However, in React, function components can return a ReactNode. This type includes number | string | Iterable | undefined and will likely also include Promise( in the future.
-
Is ESLint Exhaustive Deps a bad rule (sometimes)?
I was also hoping that useEvent would eliminate some weird dependency cases, who knows when that will actually happen (https://github.com/reactjs/rfcs/pull/220).
-
Returning to React and looking for modern expert to sanity check
Given a lot of unknowns on SSR and ReactEng working on RSC it feels like the wrong move to use next.js and I should just use normal react. For basic react is create react app the way to go or vite?
-
Server Components vs. SSR in Next.js
As mentioned before, Next.js takes a stance of treating every component as a Server Component by default. If you want to use a Client Component, you'll need to annotate the file with use client; directive at the top of the component file.
-
Is it a bad idea to use the experimental "/app" directory in a professional project?
Use client is actually a React convention for what it’s worth. https://github.com/reactjs/rfcs/pull/227
What are some alternatives?
react-app-rewired - Override create-react-app webpack configs without ejecting
server - Tolgee is translation management cloud platform made for translating modern web applications. It works great with JS frameworks like React, Angular, Vue and others. [Moved to: https://github.com/tolgee/tolgee-platform]
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
use-context-selector - React useContextSelector hook in userland
Next.js - The React Framework
react-refresh-webpack-plugin - A Webpack plugin to enable "Fast Refresh" (also previously known as Hot Reloading) for React components.
create-react-app - Set up a modern web app by running one command.
react-18 - Workgroup for React 18 release.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
react-redux - Official React bindings for Redux
vite - Next generation frontend tooling. It's fast!
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla