From 6b34fd83a80a20c11006aa36c6403328d285beb9 Mon Sep 17 00:00:00 2001 From: julien huang Date: Sat, 2 Sep 2023 20:31:40 +0200 Subject: [PATCH] docs: explain better ? --- docs/2.guide/2.directory-structure/1.components.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/2.guide/2.directory-structure/1.components.md b/docs/2.guide/2.directory-structure/1.components.md index 7bc83d5736..5c10a3a881 100644 --- a/docs/2.guide/2.directory-structure/1.components.md +++ b/docs/2.guide/2.directory-structure/1.components.md @@ -319,11 +319,11 @@ Server-only components use `` under the hood, meaning that `lazy` pr When rendering a server-only or island component, `` 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 `
` with `display: contents;`