craco VS star-history

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)

If you initiated your React application using create-react-app, leverage @craco/craco to override your webpack configuration.

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.

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.

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? :)

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.

Create react app + Craco

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.

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.

I have some questions about the Github Star history, it's very unusual to see a ~1 year old with 20k+ stars.

It went from 6k to 15k+ stars in a few days around 2023 Christmas when global internet traffic is usually lowest, and I couldn't find any major social media posts or announcements around that time. If you're gonna buy stars don't buy 10k+ stars on one day, spread it out a bit!

https://star-history.com/#Stirling-Tools/Stirling-PDF&Date

https://www.google.com/search?q=%22stirling%22+%22PDF%22&sca...

That’s a great project you pulled off. From the time I starred it (10-12h ago I think), and upon re-checking this post, you gained 500+ stars lol.

Visualized in a chart with star-history: https://star-history.com/#nilsherzig/LLocalSearch

You can actively see a fresh "hype curve" in the transformer-debugger repo that was posted a couple days ago (https://github.com/openai/transformer-debugger) (star history https://star-history.com/#openai/transformer-debugger&Date).

Regardless of the repo's stars or how valuable it really is, at the time I saw it posted to HN, it had 1.6k stars/16 hours. What channel are people listening to to star it so quickly. I'm not implying any nefariousness, mind you, I'm only wondering where all the stargazers were referred from so fast and in such volume.

I’ve been releasing open-source projects for years now, and I’ve always wanted to see how fast my Github repo is growing compared to other successful repositories on https://star-history.com/. The problem is that on Star History, I’m unable to zoom into the graph, so a new repo that has 1,000 stars cannot be compared with a big repo that has 50,000 because you can’t see how the bigger repo does in its beginning. So, I asked GPT Pilot to build this functionality. It scrapes Github repos for stargazers, saves them into the database, plots them on a graph, and enables the graph to be zoomed in and out.

i'm a one man shop in montana, competing w/ Google, Vercel & Facebook for dev mindshare

if i did what everyone else does you never would have heard of htmx

https://star-history.com/#bigskysoftware/htmx&Date

also: https://star-history.com/#bigskysoftware/htmx&facebook/react...

Similar to http://star-history.com for GitHub repos, http://like-history.ai is a tool to help generate the like history of projects on HuggingFace.co

More details: https://twitter.com/Tim_Qian/status/1730245069259575485

yeah, he was the one that really started the madness:

https://star-history.com/#bigskysoftware/htmx&bigskysoftware...

his video posted on july 7th

Github star history graph of the batch:

https://star-history.com/#trpc/trpc&termux/termux-app&respon...