Skip to content

fix: not correctly matching client component when teleporting#27633

Merged
danielroe merged 4 commits intonuxt:mainfrom
Rigo-m:fix/multiple-nuxt-client-components
Jun 15, 2024
Merged

fix: not correctly matching client component when teleporting#27633
danielroe merged 4 commits intonuxt:mainfrom
Rigo-m:fix/multiple-nuxt-client-components

Conversation

@Rigo-m
Copy link
Copy Markdown
Contributor

@Rigo-m Rigo-m commented Jun 15, 2024

🔗 Linked issue

Resolves #27210

📚 Description

Adding missing island uid when matching teleports in ssr renderer for island selective client components

@huang-julien

@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@huang-julien huang-julien self-requested a review June 15, 2024 16:00
Copy link
Copy Markdown
Member

@huang-julien huang-julien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work ! Can you revert the formatting changes ?

@Rigo-m
Copy link
Copy Markdown
Contributor Author

Rigo-m commented Jun 15, 2024

Nice work ! Can you revert the formatting changes ?

You mean formatting the whole file as it was in the first commit or remove the changed formatting in the other rows?

First time I just saved and linted the whole file, while in the second commit I ran pnpm run lint:fix

@Rigo-m
Copy link
Copy Markdown
Contributor Author

Rigo-m commented Jun 15, 2024

Think it's ok now. Can you trigger a nuxt edge channel release afterwards so I can make use of this change? I have some ideas for server components that makes sense after this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Selective client in a v-for generates many client component references

3 participants