Skip to content

fix(nuxt): add TS parenthesis and as expression for page meta extraction #32914

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 10, 2025

Conversation

huang-julien
Copy link
Member

🔗 Linked issue

#32902 (comment)

📚 Description

this PR handles additionnal TS expressions for page meta extraction

@huang-julien huang-julien requested a review from danielroe as a code owner August 9, 2025 19:41
Copy link

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

Copy link

coderabbitai bot commented Aug 9, 2025

Walkthrough

The isSerializable function in the codebase was updated to handle two additional TypeScript AST node types: TSAsExpression and ParenthesizedExpression. This allows the function to recursively process these node types by evaluating their expression property, similar to the existing handling of TSSatisfiesExpression. Corresponding tests were added to verify that page metadata extraction works correctly when TypeScript type assertions and parenthesised expressions are used in definePageMeta calls. No changes were made to the signatures or exports of public entities.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/additionnal_ts_extraction

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (3)
packages/nuxt/src/pages/utils.ts (1)

678-680: Unwrap more TS/JS wrappers to make serialisability checks more robust

Good addition. For completeness, consider unwrapping a few more harmless wrappers that often appear around literals:

  • TSTypeAssertion (angle-bracket assertions in .ts)
  • TSNonNullExpression (postfix ! non-null)
  • ChainExpression (parenthesised optional-chaining result)
    Adding these keeps behaviour consistent with your new handling of TSAsExpression and ParenthesizedExpression.

Proposed minimal change:

-  if (node.type === 'TSSatisfiesExpression' || node.type === 'TSAsExpression' || node.type === 'ParenthesizedExpression') {
+  if (
+    node.type === 'TSSatisfiesExpression' ||
+    node.type === 'TSAsExpression' ||
+    node.type === 'TSTypeAssertion' ||          // e.g. <T>'foo' in .ts (not .tsx)
+    node.type === 'TSNonNullExpression' ||      // e.g. ('foo' as const)!
+    node.type === 'ChainExpression' ||          // e.g. ('foo' as const)?.toString
+    node.type === 'ParenthesizedExpression'
+  ) {
     return isSerializable(code, node.expression)
   }

Note: Please confirm the exact node type names as emitted by oxc for your parser mode; if TSTypeAssertion isn’t emitted in your contexts, you can omit it.

packages/nuxt/test/page-metadata.test.ts (2)

156-172: Great test for TS “as” assertions; add an angle-bracket assertion case too

This validates TSAsExpression nicely. To cover the other assertion syntax in .ts (not .tsx), add a test for a TSTypeAssertion as well, e.g. name: <PageName>'name-from-page-meta'.

Example test to add elsewhere in this suite:

it('should extract metadata with TS angle-bracket type assertion', () => {
  const meta = getRouteMeta(`
  <script setup lang="ts">
  type PageName = 'name-from-page-meta' | 'whatever';
  definePageMeta({
    name: <PageName>'name-from-page-meta',
  });
  </script>
  `, filePath)

  expect(meta).toStrictEqual({ name: 'name-from-page-meta' })
})

174-188: Nit: align test title wording with AST naming

Optional: “TS ParenthesisExpression with as” could be reworded to “TS parenthesised expression with as” (human wording) or “ParenthesizedExpression with as” (AST wording) for consistency with the implementation.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce9a6a4 and 568574f.

📒 Files selected for processing (2)
  • packages/nuxt/src/pages/utils.ts (1 hunks)
  • packages/nuxt/test/page-metadata.test.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

Follow standard TypeScript conventions and best practices

Files:

  • packages/nuxt/src/pages/utils.ts
  • packages/nuxt/test/page-metadata.test.ts
**/*.{test,spec}.{ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

Write unit tests for core functionality using vitest

Files:

  • packages/nuxt/test/page-metadata.test.ts
🧠 Learnings (6)
📓 Common learnings
Learnt from: Tofandel
PR: nuxt/nuxt#0
File: :0-0
Timestamp: 2024-11-11T12:34:22.648Z
Learning: Ensure that AI-generated summaries accurately reflect the key changes in the PR, focusing on notable changes such as the removal of unused imports and variables starting with underscores.
Learnt from: GalacticHypernova
PR: nuxt/nuxt#29661
File: packages/kit/src/template.ts:227-229
Timestamp: 2024-11-28T21:22:40.496Z
Learning: In `packages/kit/src/template.ts`, when updating the `EXTENSION_RE` regular expression for TypeScript configuration, avoid using patterns like `(\.\w+)+$` as they can result in catastrophic backtracking.
📚 Learning: 2024-12-12T12:36:34.871Z
Learnt from: huang-julien
PR: nuxt/nuxt#29366
File: packages/nuxt/src/app/components/nuxt-root.vue:16-19
Timestamp: 2024-12-12T12:36:34.871Z
Learning: In `packages/nuxt/src/app/components/nuxt-root.vue`, when optimizing bundle size by conditionally importing components based on route metadata, prefer using inline conditional imports like:

```js
const IsolatedPage = route?.meta?.isolate ? defineAsyncComponent(() => import('#build/isolated-page.mjs')) : null
```

instead of wrapping the import in a computed property or importing the component unconditionally.

Applied to files:

  • packages/nuxt/src/pages/utils.ts
  • packages/nuxt/test/page-metadata.test.ts
📚 Learning: 2024-11-28T21:22:40.496Z
Learnt from: GalacticHypernova
PR: nuxt/nuxt#29661
File: packages/kit/src/template.ts:227-229
Timestamp: 2024-11-28T21:22:40.496Z
Learning: In `packages/kit/src/template.ts`, when updating the `EXTENSION_RE` regular expression for TypeScript configuration, avoid using patterns like `(\.\w+)+$` as they can result in catastrophic backtracking.

Applied to files:

  • packages/nuxt/src/pages/utils.ts
📚 Learning: 2025-07-18T16:46:07.446Z
Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{ts,tsx} : Follow standard TypeScript conventions and best practices

Applied to files:

  • packages/nuxt/src/pages/utils.ts
📚 Learning: 2025-07-18T16:46:07.446Z
Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/e2e/**/*.{ts,js} : Write end-to-end tests using Playwright and `nuxt/test-utils`

Applied to files:

  • packages/nuxt/test/page-metadata.test.ts
📚 Learning: 2025-07-18T16:46:07.446Z
Learnt from: CR
PR: nuxt/nuxt#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T16:46:07.446Z
Learning: Applies to **/*.{test,spec}.{ts,tsx,js,jsx} : Write unit tests for core functionality using `vitest`

Applied to files:

  • packages/nuxt/test/page-metadata.test.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: codeql (javascript-typescript)
  • GitHub Check: build
  • GitHub Check: code

Copy link

pkg-pr-new bot commented Aug 9, 2025

Open in StackBlitz

@nuxt/kit

npm i https://pkg.pr.new/@nuxt/kit@32914

nuxt

npm i https://pkg.pr.new/nuxt@32914

@nuxt/rspack-builder

npm i https://pkg.pr.new/@nuxt/rspack-builder@32914

@nuxt/schema

npm i https://pkg.pr.new/@nuxt/schema@32914

@nuxt/vite-builder

npm i https://pkg.pr.new/@nuxt/vite-builder@32914

@nuxt/webpack-builder

npm i https://pkg.pr.new/@nuxt/webpack-builder@32914

commit: 568574f

Copy link

codspeed-hq bot commented Aug 9, 2025

CodSpeed Performance Report

Merging #32914 will not alter performance

Comparing fix/additionnal_ts_extraction (568574f) with main (ce9a6a4)

Summary

✅ 10 untouched benchmarks

@danielroe danielroe merged commit 6ca8008 into main Aug 10, 2025
81 of 84 checks passed
@danielroe danielroe deleted the fix/additionnal_ts_extraction branch August 10, 2025 19:35
This was referenced Aug 10, 2025
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