Skip to content
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

Source Maps stopped working on Chrome 92 #29073

Closed
Florian-crg opened this issue Sep 14, 2021 · 4 comments
Closed

Source Maps stopped working on Chrome 92 #29073

Florian-crg opened this issue Sep 14, 2021 · 4 comments
Labels
bug Issue was opened via the bug report template.

Comments

@Florian-crg
Copy link

What version of Next.js are you using?

11.0.0

What version of Node.js are you using?

v12.22.1

What browser are you using?

Chrome 93.0.4577.63 (Build officiel) (arm64)

What operating system are you using?

macOS M1

How are you deploying your application?

dev mod

Describe the Bug

I did not change my package.json nor my next.config but I now get react_devtools_backend.js:4049 in my console on Chrome instead of the file and line of my console.log(). It works fine on Firefox though.

Related post on stackoverflow https://stackoverflow.com/questions/69083933/nextjs-source-maps-stopped-working-on-chrome-92

Expected Behavior

It should, like in firefox, show the line and the name of the file of the console.log()

To Reproduce

I don't really know. Probably start a new project with the same version and log then try to inspect it using Chrome

Chrome version: 93.0.4577.63 (Build officiel) (arm64)

@Florian-crg Florian-crg added the bug Issue was opened via the bug report template. label Sep 14, 2021
@oleics
Copy link

oleics commented Sep 14, 2021

Same here, disabling react-dev-tools "fixes" this for me

@ljosberinn
Copy link
Contributor

ljosberinn commented Sep 20, 2021

as far as I'm aware this is unrelated to next but actually a change in the react devtools which now monkey patch the console: facebook/react#22257 (comment)

workaround: facebook/react#22257 (comment)

@bvaughn
Copy link

bvaughn commented Sep 28, 2021

@ljosberinn is correct. We (react devtools) will be improving this experience with the next release.

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

5 participants