mirror of
https://github.com/nuxt/nuxt.git
synced 2024-11-23 06:05:11 +00:00
dc47c64f14
Co-authored-by: Daniel Roe <daniel@roe.dev> Co-authored-by: Sébastien Chopin <seb@nuxtjs.com> Co-authored-by: Pooya Parsa <pooya@pi0.io> Co-authored-by: pooya parsa <pyapar@gmail.com> Co-authored-by: Clément Ollivier <clement.o2p@gmail.com>
18 lines
1.0 KiB
Markdown
18 lines
1.0 KiB
Markdown
# Auto Imports
|
|
|
|
Nuxt 3 adopts a minimal friction approach, meaning wherever possible components and composables are auto-imported.
|
|
|
|
::alert{type=info}
|
|
In the rest of the migration documentation, you will notice that key Nuxt and Vue utilities do not have explicit imports. This is not a typo; Nuxt will automatically import them for you, and you should get full type hinting if you have followed [the instructions](/migration/configuration#typescript) to use Nuxt's TypeScript support.
|
|
::
|
|
|
|
[Read more about auto imports](/guide/concepts/auto-imports)
|
|
|
|
## Migration
|
|
|
|
1. If you have been using `@nuxt/components` in Nuxt 2, you can remove `components: true` in your `nuxt.config`. If you had a more complex setup, then note that the component options have changed somewhat. See the [components documentation](/guide/directory-structure/components) for more information.
|
|
|
|
::alert{type=info}
|
|
You can look at `.nuxt/types/components.d.ts` and `.nuxt/types/imports.d.ts` to see how Nuxt has resolved your components and composable auto-imports.
|
|
::
|