Bennett Dams

I think it's obvious that most people want a config file at project root to overwrite **specific** keys of `react-scripts`' Webpack configuration (and leave leave the rest as they are)...

The JavaScript/Prettier configuration isn't added yet, so there's no doubt that the route will produce a 404. Will leave this issue open until we've added it.

@TkDodo Thanks for the feedback and possible workaround. I could also create my own React context and save `isError` or `isLoading` there, so all components have the same status -...

@kettanaito Thanks a lot for your detailed answer, but I'm lacking knowledge to give you better feedback for that. One thing I can ask though: > You may access that...

> While the test is not marked as failed, any assertions that depend on data will fail. The request is still terminated even as of now, so if you rely...

@inian Thanks! Just to be sure: You didn't list a new option in your comment that I hadn't already mentioned in my post, right?

This issue came out of nowhere for me, took me way too long to recognize that it's a cache error. ### FIX All tests work again with adding `--no-cache` to...

Just to give a perspective from another language: One of TypeScript's main features is exactly this "object typing". It's even a main bullet point in their documentation and one of...

_(For future readers: Workarounds shown below)_ Please consider changing this to the expected behavior. As @benneq said, this causes a lot of rerenders. To my understanding, `useNavigate` does not need...

### Another workaround for conditional rendering I wanted to submit a form via `onBlur` and encountered this bug. In my case, I was conditionally rendering either the data to display...