react-app-boilerplate VS craco

This comment comes from a lot of iterations in both my work and personal projects. It's my opinion that anything modified or imported is "source code" and should this be in src/. Frankly, most of the community disagrees which is why public/ exists in the first place. Even that page you linked, while it does specify index.html should be separate, still implies index.html is a part of source code and IMO should be treated as such. Maybe it was premature for me to bring this up, but it's why I put index.html, favicon, and others in src/ in my React boilerplate repo repo. Just one of those "at discretion of the dev" type of things.

Personally, I don't like having to download files and hiring managers/interviewers have even less desire since they're usually in a rush and interviewing many candidates. I'd suggest converting your resume download button to a PDF-viewer hyperlink (e.g. Google's built-in viewer). That way, people can view your resume without having to download it while still giving them the option to download it. Or, if you want the resume to stay on your site instead of a new tab, you could always embed it instead.

Specifically, if I have particularly important, detailed, and informative information about a change, it should be saved somewhere (Jira, docs, comments, git messages, pick your poison). Assuming that "I named my variable well so everyone will always understand the tens of concepts around my thinking process" is incredibly short-sighted and will result in a bad team experience. It has to be documented somewhere. IMO git commit messages are the best b/c you can easily git blame any line in an IDE and know exactly why that line was changed, removing all relation to other lines' changes.

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.