I'm on Linux (Mint) and using the Chrome Developer Tools. Whenever I click on a file link in a stack trace (from an error, warning, etc.) ... for instance if I click on layout.js in ...
at FrontPage (webpack-internal:///./src/components/layout.js:46:11)
... Chrome then tries to open the link to:
webpack-internal:///./src/components/layout.js
Previously that would just show me the file in the Dev Tools' "Sources" tab ... but now it instead opens a prompt from xdg-open, saying "A website wants to open this application."
If I open it, I'm stuck on an empty tab for webpack-internal:///./src/components/layout.js. If I cancel, nothing happens.
Does anyone know how I can get it to go back to opening such links within the Dev Tools Sources tab?
As a Chrome developer explained here
The problem here is that part of the
Error.stackcontent contains a stack trace from the Node.js server, while you are debugging the React client (in the browser).
Our recommendation is to open a bug against next.js - they should not provide broken links to DevTools.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With