Property 'statusCode' does not exist on type 'FetchError<any>'

[misbahansori]

Environment

Node : v16.14.2
ofetch: "^1.3.2",

Reproduction

try {
    await $fetch("/contact", {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
      },
      baseURL: runtimeConfig.public.apiUrl,
      body: form.value,
    });
  } catch (error) {
    if (!(error instanceof FetchError)) throw error;

    if (error.statusCode !== 422) throw error;
              // ^Property 'statusCode' does not exist on type 'FetchError<any>'.ts(2339)
    errors.value = error.data.errors;
                                  // ^Property 'data' does not exist on type 'FetchError<any>'.ts(2339)
  }

Describe the bug

After upgrading to version 1.3.2, the following error message appears. I can confirm that the error message does not appear in version 1.3.1.

Additional context

No response

Logs

No response

[pi0]

Thanks for making issue. You can use new IFetchError type to fix. I will try to find a way to fix FetchError (class) types. We had to make this change to avoid unnecessary runtime overhead...

[sharifzadesina]

It was actually working before.
Now, even I can't access response property. Actually non of IFetchError properties.

[johannschopplich]

@misbahansori @sharifzadesina I had the same problem and provided a PR to ensure TypeScript understands and provides properties like statusCode, statusMessage etc.: #279

For my own purposes before the PR gets merged (or a better solution found 😉), you can re-export the type:

export type { IFetchError as FetchError } from 'ofetch'

Which I did in my Nuxt API Party plugin: johannschopplich/nuxt-api-party@181a5a0

[misbahansori]

In the meantime, does anyone have a good approach to narrow the types within the catch block? Since the error type is unknown we need to narrow it down. currently, I'm using error instanceof FetchError which has a runtime implication.

[pi0]

Should be resolved by #279 in v1.3.3