Skip to content

fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set#12278

Merged
lforst merged 1 commit intodevelopfrom
lforst-fix-12219
May 29, 2024
Merged

fix(nextjs): Do not hide sourceMappingURL comment on client when nextConfig.productionBrowserSourceMaps: true is set#12278
lforst merged 1 commit intodevelopfrom
lforst-fix-12219

Conversation

@lforst
Copy link
Copy Markdown
Contributor

@lforst lforst commented May 29, 2024

#12219 correctly points out that we are stomping the webpack devtool option for when people actually want to have the sourceMappingURL show up via productionBrowserSourceMaps.

With this PR, if people set productionBrowserSourceMaps in Next.js, we will not hide their sourceMappingURL comment.

Fixes #12219

…extConfig.productionBrowserSourceMaps: true` is set
@lforst lforst requested review from Lms24 and andreiborza May 29, 2024 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Client-side sourceMappingURL is being erased despite of settings

2 participants