From dce837941a4ef9fc3b8173de867ec1000b5b9372 Mon Sep 17 00:00:00 2001 From: Tobias Diez Date: Wed, 13 Oct 2021 23:32:51 +0200 Subject: [PATCH] docs: better explanation for `@nuxtjs/composition-api` replacement (#812) Co-authored-by: Daniel Roe --- docs/content/1.getting-started/3.bridge.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/1.getting-started/3.bridge.md b/docs/content/1.getting-started/3.bridge.md index b37fc5fe8a..9968e2b24b 100644 --- a/docs/content/1.getting-started/3.bridge.md +++ b/docs/content/1.getting-started/3.bridge.md @@ -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-runtime` and `nuxt-ts`: Nuxt 2 has built-in runtime support - 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