React Fir は、 React のレンダリングを完全に再設計することを目指しており

await ui = await f(await state) という新しいメンタルモデル

Errors can be divided into two categories: expected errors and uncaught exceptions.

Expected errors are those that can occur during the normal operation of the application, such as those from server-side form validation or failed requests. These errors should be handled explicitly and returned to the client.

You can use the useActionState hook to handle expected errors in Server Functions. For these errors, avoid using try/catch blocks and throw errors. Instead, model expected errors as return values.

Uncaught exceptions are unexpected errors that indicate bugs or issues that should not occur during the normal flow of your application. These should be handled by throwing errors, which will then be caught by error boundaries.

Errors will bubble up to the nearest parent error boundary. This allows for granular error handling by placing error.tsx files at different levels in the route hierarchy.

Error boundaries don’t catch errors inside event handlers. They’re designed to catch errors during rendering to show a fallback UI instead of crashing the whole app.

A Server Function is an asynchronous function that runs on the server. They can be called from client through a network request, which is why they must be asynchronous. In an action or mutation context, they are also called Server Actions.

"workbench.layoutControl.enabled": false