Skip to content

fix(nuxt): add sourcemap path transformation for client builds #32313

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

peterbud
Copy link

@peterbud peterbud commented Jun 5, 2025

🔗 Linked issue

Resolves #32009

📚 Description

This change fixes the source map paths in client builds, to point them to the right sourcemaps.

My first contribution to this repo, pls check if I used the nuxt config dirs properly.

Question: should I add a test for checking the generated sourcemap content? I have seen that all fixtures have disabled sourcemaps, so maybe I need to add a new fixture? LMK!

@Copilot Copilot AI review requested due to automatic review settings June 5, 2025 21:15
@peterbud peterbud requested a review from danielroe as a code owner June 5, 2025 21:15
Copy link

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

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 ensures client build source maps point to the final output directory by transforming their paths.

  • Added sourcemapPathTransform to adjust source map paths from the temp build directory to .output/public.
  • Imported dirname and relative from pathe to compute the correct relative paths.
  • Used ctx.config.root! and ctx.nuxt.options.app.buildAssetsDir to locate the public assets directory.
Comments suppressed due to low confidence (3)

packages/vite/src/client.ts:181

  • [nitpick] The variable name newRelativePath is generic; consider renaming to outputRelativePath to clarify that this path targets the final output directory.
const newRelativePath = relative(

packages/vite/src/client.ts:175

  • Add unit tests covering sourcemapPathTransform for both relative and non-relative source paths to ensure correct behavior across different build scenarios.
sourcemapPathTransform (relativeSourcePath, sourcemapPath) {

packages/vite/src/client.ts:175

  • [nitpick] Include a JSDoc comment above sourcemapPathTransform describing its purpose, parameters, and return value to aid future maintainers.
sourcemapPathTransform (relativeSourcePath, sourcemapPath) {

if (relativeSourcePath.startsWith('..')) {
const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
const newRelativePath = relative(
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
Copy link
Preview

Copilot AI Jun 5, 2025

Choose a reason for hiding this comment

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

Avoid hardcoding '.output/public'; derive the public output path from Nuxt config or extract it into a shared constant to prevent divergence if the output directory structure changes.

Suggested change
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
join(ctx.config.root!, getPublicOutputPath(ctx.nuxt.options), ctx.nuxt.options.app.buildAssetsDir),

Copilot uses AI. Check for mistakes.

if (relativeSourcePath.startsWith('..')) {
const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
const newRelativePath = relative(
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
Copy link
Preview

Copilot AI Jun 5, 2025

Choose a reason for hiding this comment

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

Avoid using the non-null assertion (!) on ctx.config.root; consider validating or providing a fallback to prevent potential runtime errors if root is ever undefined.

Suggested change
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
join(ctx.config.root ?? '', '.output/public', ctx.nuxt.options.app.buildAssetsDir),

Copilot uses AI. Check for mistakes.

Copy link

pkg-pr-new bot commented Jun 5, 2025

Open in StackBlitz

@nuxt/kit

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

nuxt

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

@nuxt/rspack-builder

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

@nuxt/schema

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

@nuxt/vite-builder

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

@nuxt/webpack-builder

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

commit: 2f3cd70

Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

A new function, sourcemapPathTransform, has been added to the Rollup output options within the client build configuration. This function modifies source map paths during the client build by recalculating paths that start with ".." to be relative to the final public build directory, ensuring correct mapping from the output location. The implementation uses dirname and relative functions from the pathe module, with the import statement updated accordingly. No changes were made to exported or public entity declarations; all modifications are internal to the buildClient function.

✨ 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: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 42114f4 and 2f3cd70.

📒 Files selected for processing (1)
  • packages/vite/src/client.ts (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: code
🔇 Additional comments (1)
packages/vite/src/client.ts (1)

2-2: LGTM! Import statement correctly updated.

The import statement appropriately adds dirname and relative functions from the pathe module, which are used in the new sourcemap transformation logic below.

Comment on lines +175 to +188
sourcemapPathTransform (relativeSourcePath, sourcemapPath) {
// client build is running in a temporary build directory, like `.nuxt/dist/client`
// so we need to transform the sourcemap path to be relative to the final build directory
// which is normally `.output/public`
if (relativeSourcePath.startsWith('..')) {
const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
const newRelativePath = relative(
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
absoluteSourcePath,
)
return newRelativePath
}
return relativeSourcePath
},
Copy link

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify ctx.config.root availability and consider path construction robustness.

The sourcemap path transformation logic is well-implemented and addresses the core issue of ensuring source maps point to correct locations relative to the final build directory. However, there's a potential safety concern with the non-null assertion operator.

The path construction logic correctly handles the transformation from temporary build directories to final output locations. The conditional check for paths starting with ".." appropriately identifies source paths that need transformation, whilst preserving paths that are already correctly relative to the build directory.


🏁 Script executed:

#!/bin/bash
# Description: Verify that ctx.config.root is always defined in the buildClient context
# Expected: ctx.config.root should be consistently available, otherwise the non-null assertion could cause runtime errors

ast-grep --pattern $'buildClient($$$) {
  $$$
  ctx.config.root
  $$$
}'

Length of output: 73


I wasn’t able to confirm that ctx.config.root is always set from the first grep. Let’s locate the buildClient definition and see how ctx is typed and where config.root comes from:


🏁 Script executed:

#!/bin/bash
# Locate and inspect buildClient and config.root usage in client.ts
rg -n "function buildClient" -n packages/vite/src/client.ts
rg -n "ctx.config.root" -n packages/vite/src/client.ts

Length of output: 274


Let’s inspect the top of client.ts to see where ViteBuildContext comes from and find its definition:


🏁 Script executed:

#!/bin/bash
# Show imports and type of buildClient
sed -n '1,50p' packages/vite/src/client.ts

# Locate ViteBuildContext definition across the repo
rg -n "ViteBuildContext" -n .

Length of output: 3644


Let’s inspect the ViteBuildContext interface and its instantiation to see how config.root is set:


🏁 Script executed:

#!/bin/bash
# Show the ViteBuildContext interface
rg -n "export interface ViteBuildContext" -n packages/vite/src/vite.ts
sed -n '23,80p' packages/vite/src/vite.ts

# Find where ctx is created and how config.root is assigned
rg -n "const ctx: ViteBuildContext" -n packages/vite/src/vite.ts
sed -n '61,150p' packages/vite/src/vite.ts

Length of output: 5733


Add a safe default for config.root to avoid runtime errors

The ctx.config.root! non-null assertion may be undefined since we never set root in the base Vite config. Please either inject a default root when creating the context or use a fallback in the path transform.

File: packages/vite/src/client.ts
Lines: 175–188

Suggested changes:

       sourcemapPathTransform (relativeSourcePath, sourcemapPath) {
         if (relativeSourcePath.startsWith('..')) {
           const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
-          const newRelativePath = relative(
-            join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
-            absoluteSourcePath,
-          )
+          // Use config.root if set, otherwise fall back to Nuxt’s rootDir
+          const buildRoot = ctx.config.root ?? ctx.nuxt.options.rootDir
+          const newRelativePath = relative(
+            join(buildRoot, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
+            absoluteSourcePath,
+          )
           return newRelativePath
         }
         return relativeSourcePath
       },

Alternatively, in packages/vite/src/vite.ts add root: nuxt.options.rootDir to the default config passed to vite.mergeConfig.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
sourcemapPathTransform (relativeSourcePath, sourcemapPath) {
// client build is running in a temporary build directory, like `.nuxt/dist/client`
// so we need to transform the sourcemap path to be relative to the final build directory
// which is normally `.output/public`
if (relativeSourcePath.startsWith('..')) {
const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
const newRelativePath = relative(
join(ctx.config.root!, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
absoluteSourcePath,
)
return newRelativePath
}
return relativeSourcePath
},
sourcemapPathTransform (relativeSourcePath, sourcemapPath) {
// client build is running in a temporary build directory, like `.nuxt/dist/client`
// so we need to transform the sourcemap path to be relative to the final build directory
// which is normally `.output/public`
if (relativeSourcePath.startsWith('..')) {
const absoluteSourcePath = resolve(dirname(sourcemapPath), relativeSourcePath)
// Use config.root if set, otherwise fall back to Nuxt’s rootDir
const buildRoot = ctx.config.root ?? ctx.nuxt.options.rootDir
const newRelativePath = relative(
join(buildRoot, '.output/public', ctx.nuxt.options.app.buildAssetsDir),
absoluteSourcePath,
)
return newRelativePath
}
return relativeSourcePath
},
🤖 Prompt for AI Agents
In packages/vite/src/client.ts around lines 175 to 188, the code uses a non-null
assertion on ctx.config.root which may be undefined and cause runtime errors. To
fix this, ensure ctx.config.root is always defined by either injecting a default
root value when creating the context or by adding a safe fallback in the
sourcemapPathTransform function before using ctx.config.root. Alternatively, set
root: nuxt.options.rootDir in the default config passed to vite.mergeConfig in
packages/vite/src/vite.ts to guarantee root is always present.

Copy link

codspeed-hq bot commented Jun 5, 2025

CodSpeed Performance Report

Merging #32313 will not alter performance

Comparing peterbud:32009 (2f3cd70) with main (42114f4)

Summary

✅ 10 untouched benchmarks

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.

Invalid relative paths in sourcemap "sources" under .output/public
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