* docs: implement new website theme * chore: rename dirs * chore: update build * lint fix * chore: update deps * fix: include node_modules in esbuild step * chore: update deps * Update .gitignore * chore: update theme version * up * up * fix: use svg for illustration * chore: update to 0.0.12 * chore: force parse5 resolution * stay with build * feat: always display first home section * Update yarn.lock * chore: update theme * fix lint * docs: update home title * chore: update website theme version * Update docs/content/0.index.md Co-authored-by: pooya parsa <pyapar@gmail.com> * Update docs/content/0.index.md Co-authored-by: pooya parsa <pyapar@gmail.com> * up * chore: bump theme version * up * chore: up * up up and up * chore: generate * fix: boolean value * feat: new images * update again * chore: up * ouep * chore: up Co-authored-by: Daniel Roe <daniel@roe.dev> Co-authored-by: Clément Ollivier <clement.o2p@gmail.com> Co-authored-by: pooya parsa <pyapar@gmail.com>
2.9 KiB
navigation.icon | title | head.title | description |
---|---|---|---|
IconDirectory | composables | Composables | Use the composables/ directory to auto-import your Vue composables into your application. |
Composables Directory
Nuxt 3 uses the composables/
directory to automatically import your Vue composables into your application using auto-imports!
Under the hood, Nuxt auto generates the file .nuxt/imports.d.ts
to declare the types.
Be aware that you have to run nuxi prepare
, nuxi dev
or nuxi build
in order to let Nuxt generate the types. If you create a composable without having the dev server running, TypeScript will throw an error, such as Cannot find name 'useBar'.
Usage
Method 1: Using named export
export const useFoo = () => {
return useState('foo', () => 'bar')
}
Method 2: Using default export
// It will be available as useFoo() (camelCase of file name without extension)
export default function () {
return useState('foo', () => 'bar')
}
Usage: You can now use auto imported composable in .js
, .ts
and .vue
files
<template>
<div>
{{ foo }}
</div>
</template>
<script setup>
const foo = useFoo()
</script>
::LinkExample{link="/docs/examples/auto-imports/composables"} ::
Examples
Nested Composables
You can use a composable within another composable using auto imports:
export const useFoo = () => {
const nuxtApp = useNuxtApp()
const bar = useBar()
}
Access plugin injections
You can access plugin injections from composables:
export const useHello = () => {
const nuxtApp = useNuxtApp()
return nuxtApp.$hello
}
How Files Are Scanned
Nuxt only scans files at the top level of the composables/
directory, e.g.:
composables
| - index.ts // scanned
| - useFoo.ts // scanned
| - nested
| --- utils.ts // not scanned
Only composables/index.ts
and composables/useFoo.ts
would be searched for imports.
To get auto imports working for nested modules, you could either re-export them (recommended) or configure the scanner to include nested directories:
Example: Re-export the composables you need from the composables/index.ts
file:
// Enables auto import for this export
export { utils } from './nested/utils.ts'
Example: Scan nested directories inside the composables/
folder:
export default defineNuxtConfig({
imports: {
dirs: [
// Scan top-level modules
'composables',
// ... or scan modules nested one level deep with a specific name and file extension
'composables/*/index.{ts,js,mjs,mts}',
// ... or scan all modules within given directory
'composables/**'
]
}
})