Skip to content

fix(nuxt): ignore definePageMeta warning for client only pages in dev#28246

Merged
danielroe merged 5 commits intomainfrom
fix/dev_clientonlypagewarning
Jul 21, 2024
Merged

fix(nuxt): ignore definePageMeta warning for client only pages in dev#28246
danielroe merged 5 commits intomainfrom
fix/dev_clientonlypagewarning

Conversation

@huang-julien
Copy link
Copy Markdown
Member

🔗 Linked issue

📚 Description

Hi 👋 this PR fix an issue with #27839
Since the wrapper is being rendered as the route component for client-pages, we need to mark clientonly page components so definePageMeta can ignore it in dev

@huang-julien huang-julien requested a review from danielroe as a code owner July 21, 2024 13:52
@bolt-new-by-stackblitz
Copy link
Copy Markdown

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

@danielroe
Copy link
Copy Markdown
Member

Is the issue here that page metadata isn't respected for client-only pages?

@huang-julien
Copy link
Copy Markdown
Member Author

The issue is that component is the wrapper returned from createClientPage while definePageMeta is called from the page component. So it means that conditions in the if statement will never be true for client only pages

@danielroe
Copy link
Copy Markdown
Member

Oh, just wondering why you linked #27839.

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.

2 participants