Upgrade to nuxt-bridge: Auto-imports cause eslint errors

341 views Asked by At

I want to upgrade a nuxt v2.16 project to v2.17 and nuxt-bridge and replace the @nuxt/composition-api with the core composition api.

Now I have autoimports and this code for example runs:

// ...
  setup(props) {
    const { content } = toRefs(props)
    const { env, $axios, $moment } = useNuxtApp()
    const filters = ref()
    const fetching = ref(false)

but eslint still complains about these: toRefs, useNuxtApp, ref like 'useNuxtApp' is not defined. eslint no-undef.

How can I overcome this problem? I think the eslint should take into account that it should not complain about auto-imports.

0

There are 0 answers