Skip to content

fix(kit): do not double-urlify file urls when resolving schema #32354

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 2 commits into from
Jun 10, 2025

Conversation

danielroe
Copy link
Member

🔗 Linked issue

resolves #32311

📚 Description

we were wrongly converting file URLs to file URLs, meaning nuxt/schema wasn't being resolved from within the nuxt directory.

@Copilot Copilot AI review requested due to automatic review settings June 10, 2025 11:34
Copy link

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

Copy link

coderabbitai bot commented Jun 10, 2025

Walkthrough

The import of pathToFileURL from 'node:url' was removed. In the loadNuxtSchema function, the urls array was explicitly typed as Array<URL | string>. The logic for adding the Nuxt module path to the urls array was changed: previously, the Nuxt path was converted to a file URL using pathToFileURL before being unshifted; now, the raw nuxtPath (which may be a string or URL) is directly unshifted without conversion. No changes were made to the signatures or declarations of exported or public entities. The rest of the function and related logic remain unchanged.


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 67c04eb and 2c05c7e.

📒 Files selected for processing (1)
  • packages/kit/src/loader/config.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/kit/src/loader/config.ts
⏰ Context from checks skipped due to timeout of 90000ms (20)
  • GitHub Check: test-fixtures (windows-latest, built, webpack, default, manifest-on, json, 20)
  • GitHub Check: test-fixtures (windows-latest, built, vite, async, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, rspack, default, manifest-on, json, 20)
  • GitHub Check: test-fixtures (windows-latest, dev, vite, async, manifest-off, json, 20)
  • GitHub Check: test-fixtures (windows-latest, dev, vite, async, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, webpack, async, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, webpack, default, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, rspack, async, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, vite, default, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-off, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, js, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, dev, vite, default, manifest-off, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, vite, default, manifest-off, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-off, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, dev, vite, default, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, built, vite, async, manifest-on, json, 20)
  • GitHub Check: test-fixtures (ubuntu-latest, dev, vite, async, manifest-on, json, 20)
  • GitHub Check: test-benchmark
  • GitHub Check: typecheck (windows-latest, bundler)
  • GitHub Check: typecheck (ubuntu-latest, bundler)
✨ Finishing Touches
  • 📝 Generate Docstrings

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.
    • @coderabbitai modularize this function.
  • 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 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 (1)
packages/kit/src/loader/config.ts (1)

11-11: Remove unused resolveModulePath import
The resolveModulePath symbol is imported but never used in this module. Consider removing it to reduce dead code and improve clarity.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a14e790 and 67c04eb.

📒 Files selected for processing (1)
  • packages/kit/src/loader/config.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: codeql (actions)
  • GitHub Check: codeql (javascript-typescript)
  • GitHub Check: build
  • GitHub Check: code
🔇 Additional comments (2)
packages/kit/src/loader/config.ts (2)

126-126: Explicit union type for urls improves clarity
Typing urls as Array<URL | string> clearly documents that it may contain both file URLs and raw paths.


129-129: Prevent double-urlification by unshifting raw nuxtPath
Directly adding nuxtPath fixes the double-URL conversion bug. Please verify that resolveModuleURL accepts an array for its from option to guarantee proper schema resolution.

Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes an issue where file URLs were being converted twice when resolving @nuxt/schema, causing resolution failures within the Nuxt directory.

  • Added resolveModulePath import and adjusted module URL resolution logic
  • Changed urls array to accept both URL and string types
  • Removed redundant pathToFileURL conversion for already-resolved module paths
Comments suppressed due to low confidence (1)

packages/kit/src/loader/config.ts:127

  • Add a unit test to cover both string and URL inputs for loadNuxtSchema, ensuring file URLs are not double-urlified when resolving @nuxt/schema.
const nuxtPath = resolveModuleURL('nuxt', { try: true, from: url })

Copy link

pkg-pr-new bot commented Jun 10, 2025

Open in StackBlitz

@nuxt/kit

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

nuxt

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

@nuxt/rspack-builder

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

@nuxt/schema

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

@nuxt/vite-builder

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

@nuxt/webpack-builder

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

commit: 2c05c7e

Copy link

codspeed-hq bot commented Jun 10, 2025

CodSpeed Performance Report

Merging #32354 will not alter performance

Comparing fix/resolve-schema (2c05c7e) with main (a14e790)

Summary

✅ 10 untouched benchmarks

@danielroe danielroe merged commit 0f7d877 into main Jun 10, 2025
117 of 120 checks passed
@danielroe danielroe deleted the fix/resolve-schema branch June 10, 2025 12:45
@github-actions github-actions bot mentioned this pull request Jun 10, 2025
@github-actions github-actions bot mentioned this pull request Jul 1, 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.

Nuxt 4.0.0.-alpha.1: compatibilityVersion reverting to 3 with Nuxt UI (and probably other modules)
1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy