Handle more known protocols in stackframe locations#76085
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Failing test suitesCommit: c1e35fc
Expand output● use-cache-close-over-function › should show the error overlay for server-side usage Read more about building and testing Next.js in contributing.md.
Expand output● ReactRefreshLogBox app default › server component can recover from error thrown in the module Read more about building and testing Next.js in contributing.md. |
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
build cache
Diff detailsDiff for main-HASH.jsDiff too large to display Diff for app-page-exp..ntime.dev.jsDiff too large to display Diff for app-page.runtime.dev.jsDiff too large to display |
b8f4b3d to
0ec9937
Compare
Adds support for `turbopack:`, `rsc:`, and `webpack-internal:`. It should really just parse any valid URL scheme. Riskier and harder to implement for Gecko though so restricting this fix to known cases for now.
87f3d0c to
c1e35fc
Compare

Adds support for
turbopack:,rsc:, andwebpack-internal:.Now we no longer need to manually hide
rsc:in file locations since that was a bug that was just masked.It should really just parse any valid URL scheme.
Riskier and harder to implement for Gecko though so
restricting this fix to known cases for now.