react.dev

There’s always the extra idiomatic __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED for coworkers that can’t take a hint. https://github.com/reactjs/react.dev/issues/3896

"unsafe" seems quite different from the "dangerously [...]" phrasal template. I don't think it's a stretch to suppose it was inspired by React. Still waiting for this one to catch on: React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED https://github.com/reactjs/react.dev/issues/3896

Hi! I played a major part in getting that "installation" page rewritten to actually mention other tools like Vite :) The general TLDR is: - CRA was listed in the _old_ docs site - The new docs site coincided with the React team emphasizing "frameworks" to provide an all-in-one build experience and hopefully lead to better apps. - That also meant no ala-carte build tools were listed. This made many people (including me) unhappy. - CRA broke when React 19 came out in Dec 2024. This caused problems for beginners. - I pushed the React team to both deprecate CRA and finally rewrite the setup pages to list other build tools as valid options. I wrote up a much longer background of what happened around the "frameworks" push and this docs page here: - https://blog.isquaredsoftware.com/2025/06/react-community-20... And here's the issue I filed push

Thanks for the feedback, I adjusted it here so the first note is related to the impacted versions: https://github.com/reactjs/react.dev/pull/8195

> it certainly works Not for this guy: https://github.com/reactjs/react.dev/issues/3896

I don't understand why people advocate so strongly for `--dangerously-skip-permissions`. Setting up "permissions.allow" in `.claude/settings.local.json` takes minimal time. Claude even lets you configure this while approving code, and you can use wildcards like "Bash(timeout:*)". This is far safer than risking disasters like dropping a staging database or deleting all unstaged code, which Claude would do last week, if I were running it in the YOLO mode. The worst part is seeing READMEs in popular GitHub repos telling people to run YOLO mode without explaining the tradeoffs. They just say, "Run with these parameters, and you're all good, bruh," without any warning about the risks. I wish they could change the parameter to signify how scary it can be, just like React did with React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED (https:/

> I don't understand Well. This is hardly the funniest example then. Check this one out: https://github.com/reactjs/react.dev/issues/3896

Of course, it doesn't stop people from asking if they can use it: https://github.com/reactjs/react.dev/issues/3896

I genuinely thought CRA had been deprecated and development had ended a couple of years ago? Edit: Maybe it just stopped being a recommendation in the React Docs? https://github.com/reactjs/react.dev/pull/5487

That doesn't always help[0] [0] https://github.com/reactjs/react.dev/issues/3896

https://github.com/reactjs/react.dev/issues/3896 (I do generally agree with your point.)

Reminds me of this ticket [0]. No matter how hard you try to tell people things, sometimes you just can't. [0] https://github.com/reactjs/react.dev/issues/3896