Bug: NuxtAxiosInstance no longer exported

[silverbackdan]

Issue

The interface is no longer exported from type definitions and also results in an issue with the vuex.d.ts file:
https://github.com/nuxt-community/axios-module/blob/main/types/vuex.d.ts as this will try to import it as well.

Solution:

NuxtAxiosInstance should be exported here:
https://github.com/nuxt-community/axios-module/blob/main/types/index.d.ts

Related and possibly related:

• isAxiosError is undefined on NuxtAxiosInstance #550 (could be mis-diagnosis because it does extend AxiosStatic, so perhaps the type isn't imported for this user)
• ESLint: NuxtAxiosInstance not found in '@nuxtjs/axios'(import/named) #547 (same issue)
• Property 'get' does not exist on type 'NuxtAxiosInstance' #545 possible mis-diagnosis again as it should extend Axios interfaces which includes get

[dubst3pp4]

Also affects our projects with nuxt 2.15.8 and @nuxtjs/axios 5.13.6.

[ThomasBerne]

I have the same problem

[cane-bt]

I have the same problem in Same version as the quote below.

Also affects our projects with nuxt 2.15.8 and @nuxtjs/axios 5.13.6.

I got the following errors by vscode.

Module '"@nuxtjs/axios"' has no exported member '$axios'.

or

NuxtAxiosInstance not found in '@nuxtjs/axios'

Could anyone Help me?

[silverbackdan]

Ping @pi0 (sorry I know you've been very helpful on issues in the past, thought I'd bring this to your attention in case it's a quick fix or you may ping someone who is best placed to take a look?)

[amirhoseinsalimi]

The solution is to use import type like so:

import type { NuxtAxiosInstance } from '@nuxtjs/axios';

[silverbackdan]

Hi @amirhoseinsalimi

The NuxtAxiosInstance is not being exported to be able to import as a type.

Now it is here:
https://github.com/nuxt-community/axios-module/blob/main/types/index.d.ts#L6

It should be export interface NuxtAxiosInstance ... to work no?

[amirhoseinsalimi]

Hi @silverbackdan

I'm not 100% sure why the import type works but I think there's a so-called automatic type resolution mechanism that does this favor for us, so we can import non-exported types without any hassle. Also, I did some practices on my own, and find out that if a file is a type declaration file and uses import/export syntax (which turns it into a module), this automatic type resolution mechanism becomes enabled.

Remember that using a single import or export keyword, turns a file into a module.

Maybe a TypeScript expert can help more.

[silverbackdan]

@amirhoseinsalimi How cool. Thanks for your time investigating and the solution. It's certainly resolved the issue for me so will close the issue and the detail you've given will stick with me for any type imports in future too. You rock.

[amirhoseinsalimi]

Thank YOU for asking this so I could think more about types :D. I'll update this thread once I get more information about this behavior.