fix(nuxt): Use virtual module for Nuxt pages data (SSR route parametrization)#20020
fix(nuxt): Use virtual module for Nuxt pages data (SSR route parametrization)#20020
Conversation
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Deps
Other
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧Core
Deps
Deps Dev
Other
🤖 This preview updates automatically when you update the PR. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| filename: 'sentry--nuxt-pages-data.mjs', | ||
| getContents: () => `export default ${JSON.stringify(pagesData, null, 2)};`, | ||
| }); | ||
| } |
There was a problem hiding this comment.
Fix PR missing regression test for virtual module
Low Severity
This is a fix PR that introduces a new virtual module strategy for Nuxt v4+ and a new legacy plugin file, but doesn't include any unit, integration, or E2E test to validate the regression (SSR route parametrization issue #20010). Adding a test that verifies the virtual module approach works for Nuxt v4+ and the template fallback for Nuxt v3 would help prevent regressions.
Additional Locations (1)
Triggered by project rule: PR Review Guidelines for Cursor Bot
There was a problem hiding this comment.
We have Nuxt 4 tests already covering that
size-limit report 📦
|


Creates a virtual module with Vite when using Nuxt 4+ instead of creating a template.
useServerTemplate()cannot be used here as it's not Nitro-only but the SSR-space (server) within Nuxt.Closes #20010