Sebastian Markbåge
Sebastian Markbåge
A tangentially related problem is that there's a lot of responsibility put on users of try/catch, async, promises and error boundaries. To ensure that the error gets propagated to the...
> I'd consider this a bug in the 3rd party library The issue with bugs like this (unhandled Promises being the most common), is how do you find them if...
@Bazzer588 The general recommendation is to `useReducer`. That said, your particular example can be solved like this but it is pretty unusual to not depend on any props so this...
What's this for?
I believe we can type `notFound()` and `redirect()` with the return type `: never`. That way this should work without type errors: ```tsx import { notFound } from 'next/navigation'; const...
Wait for the RFC.
Our RFCs are almost never written before code. We iterate before we're comfortable with it. We don't just publish any first idea that comes to us.
Neat. I had just started a branch to do the same. Yea this is the right direction.
Hm. It's unfortunate to expose this only in DEV when it's prod on the client. Maybe we'll do the full stacks but those are really slow to generate and there...
I think the question is not about direction per se (the error message already tells you to use startTransition) - but why. > Why does react log this error? Is...