Conversation
…cal-storage fix: skip stats layout sync for demo users
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting
| export default defineNuxtPlugin((nuxtApp) => { | ||
| for (const [name, loader] of Object.entries(components)) { | ||
| nuxtApp.vueApp.component( | ||
| name, | ||
| defineAsyncComponent({ | ||
| loader: async () => (await loader()).default, |
There was a problem hiding this comment.
The new plugin registers Dialog, Drawer, DataTable, etc. via defineAsyncComponent, but the file is suffixed with .client.ts and nuxt.config.ts now excludes these components from PrimeVue’s auto-import list. Because ssr remains enabled, the server renderer no longer registers these components and pages that render <Dialog> or <DataTable> outside <ClientOnly> (e.g. components/AccountDeleteModal.vue) will log Failed to resolve component and render empty shells until hydration. Consider registering the components in a shared (client and server) plugin or keep them in the auto-import list so SSR can resolve them.
Useful? React with 👍 / 👎.
1 participant
変更内容
確認事項
forEach使用時はインデックスを利用しているか確認、それ以外はforを利用pnpm build/pnpm previewが成功