✔️ Deploy Preview for nuxt3-docs canceled.

🔨 Explore the source changes: cebd845

🔍 Inspect the deploy log: https://app.netlify.com/sites/nuxt3-docs/deploys/619e96a8e7e17a000737e00a

By changing flatten structure of payload into { data, error?, pending? } for each key, we are increasing HTML size.

• pending state is really a runtime-specific flag to indicate we have a pending promise and is available as nuxt.App._asyncDataPromises. It should not be hydrated and useLazy* composables need to set it to true (and false if hydrated).

• error should be explicitly consumed by by user (to display in component or log). Adding it to payload, not only reduces performance but also adds security risk of exposing server errors to public. PS: A client-side retry strategy can be used to obtain payload for errors like timeouts.

• error should be explicitly consumed by by user (to display in component or log). Adding it to payload, not only reduces performance but also adds security risk of exposing server errors to public. PS: A client-side retry strategy can be used to obtain payload for errors like timeouts.

@pi0

const { error } = await useFetch('https://jsonplaceholder.typicode.com/404');

This line of code can run on both server and client with the same result and I can say that the server error for this action is already public so it was completely unrelated to Nuxt. I just want to get the http status code(404 in this case) and those recent commits transformed it from FetchError to Boolean then how can we get the status code on client side?https://stackblitz.com/edit/github-ygz9df-hnnre8?file=app.vue