Zengtudor/Nuxt
1
0
Fork 0
mirror of https://github.com/nuxt/nuxt.git synced 2024-12-02 10:27:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: explain better ?

Browse Source
This commit is contained in:
julien huang 2023-09-02 20:31:40 +02:00
parent 263b5e0066
commit 6b34fd83a8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/2.guide/2.directory-structure/1.components.md
View File

@ -319,11 +319,11 @@ Server-only components use `<NuxtIsland>` under the hood, meaning that `lazy` pr
When rendering a server-only or island component, `<NuxtIsland>` makes a HTTP request to GET a `NuxtIslandResponse`.
This means:
- You can't access to the island context from your SSR app and you can't access to your SSR app context from the island component. Both are different context.
- A new Vue app will be created server-side to create the `NuxtIslandResponse`.
- You can't access to the island app context from your SSR app and you can't access to your SSR app context from the island component. Both are different context.
- Plugins will be ran for the island Vue app except those marked with `env.island: false` on an object plugin.
You can access to an island context during the island component rendering through `nuxtApp.ssrContext.islandContext`.
You can access to an island context within an island component through `nuxtApp.ssrContext.islandContext`.
::alert{type=info}
Slots can be interactive and are wrapped within a `<div>` with `display: contents;`