You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the directions in the guide, I am unable to hit breakpoints in Code for the React application. I've found no way, using Next 8, to get source maps emitted, and I think that is likely related. As it stands when I launch Chrome from Code, nothing happens. Also when launching from Code, you don't get all of your Chrome plugins, so I have tried using an attach process and starting Chrome with CLI parameters for debugging, and that does not work either.
Any input would be appreciated - I think the docs need to be updated to better reflect the complete set of requirements around debugging.
The text was updated successfully, but these errors were encountered:
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
locked as resolved and limited conversation to collaborators
Jan 31, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After following the directions in the guide, I am unable to hit breakpoints in Code for the React application. I've found no way, using Next 8, to get source maps emitted, and I think that is likely related. As it stands when I launch Chrome from Code, nothing happens. Also when launching from Code, you don't get all of your Chrome plugins, so I have tried using an attach process and starting Chrome with CLI parameters for debugging, and that does not work either.
Any input would be appreciated - I think the docs need to be updated to better reflect the complete set of requirements around debugging.
The text was updated successfully, but these errors were encountered: