Skip to content

[DevTools Bug]: symbolicated sourcemaps won't fetch for rsc components on Chrome 135.0.7 (rsc:// and webpack:// prefixed fetches fail) #32835

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
jamiesunderland opened this issue Apr 9, 2025 · 0 comments
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug

Comments

@jamiesunderland
Copy link

jamiesunderland commented Apr 9, 2025

Website or app

localhost:3000

Repro steps

Download latest chrome (135.0.7049.85). Tested on Apple Silicon.
Start fresh next project (15.2.3+).

fileFetcher will fail to fetch resources when you inspect the default page.tsx component.

This is a really annoying bug because it ends up giving the unsymbolicated source map line number + column number, which is deceptive.

fileFetcher.js:1 Fetch API cannot load rsc://React/Server/webpack-internal:///(rsc)/app/page.tsx?19. URL scheme "rsc" is not supported.

fileFetcher.js:1 Fetch API cannot load webpack-internal:///(app-pages-browser)/node_modules/next/dist/client/image-component.js. URL scheme "webpack-internal" is not supported.

Would love for _debugSource to come back 😢

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)


Error component stack (automated)


GitHub query string (automated)


@jamiesunderland jamiesunderland added Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug labels Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug
Projects
None yet
Development

No branches or pull requests

1 participant