docs: better explanation for @nuxtjs/composition-api replacement (#812)

Co-authored-by: Daniel Roe <daniel@roe.dev>
This commit is contained in:
Tobias Diez 2021-10-13 23:32:51 +02:00 committed by GitHub
parent 9bef30d202
commit dce837941a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -118,7 +118,7 @@ Avoid the usage of `__dirname` and `__filename` as much as possible.
- Remove `@nuxt/typescript-build`: Bridge enables same functionality - Remove `@nuxt/typescript-build`: Bridge enables same functionality
- Remove `@nuxt/typescript-runtime` and `nuxt-ts`: Nuxt 2 has built-in runtime support - Remove `@nuxt/typescript-runtime` and `nuxt-ts`: Nuxt 2 has built-in runtime support
- Remove `@nuxt/nitro`: Bridge injects same functionality - Remove `@nuxt/nitro`: Bridge injects same functionality
- Remove `@nuxtjs/composition-api`: Bridge provides a Nuxt 3 compatible composition-api layer and help to remove dependency - Remove `@nuxtjs/composition-api` from your dependencies (and from your modules in `nuxt.config`). Bridge provides a legacy composition API layer that handles imports within your files from `@nuxtjs/composition-api` until you've fully finished migrating to native Bridge/Nuxt 3 composables (which you will import from by `#app`, or via auto-imports).
### Exclude Nuxt build folder from git ### Exclude Nuxt build folder from git