We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue can be traced back to this Issue: vercel/next.js#59457 (comment)
Currently, the lack of __debugSource in the app router makes it impossible to trace the component file path.
__debugSource
You can try adding @babel/plugin-transform-react-jsx-source or @react-dev-inspector/babel-plugin to .babelrc.js or babel.config.js:
@babel/plugin-transform-react-jsx-source
@react-dev-inspector/babel-plugin
.babelrc.js
babel.config.js
// https://nextjs.org/docs/advanced-features/customizing-babel-config module.exports = { presets: [ 'next/babel', ], plugins: [ '@react-dev-inspector/babel-plugin', ], }
For more information, please refer to: https://react-dev-inspector.zthxxx.me/docs/compiler-plugin
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This issue can be traced back to this Issue: vercel/next.js#59457 (comment)
Currently, the lack of
__debugSource
in the app router makes it impossible to trace the component file path.You can try adding
@babel/plugin-transform-react-jsx-source
or@react-dev-inspector/babel-plugin
to.babelrc.js
orbabel.config.js
:For more information, please refer to: https://react-dev-inspector.zthxxx.me/docs/compiler-plugin
The text was updated successfully, but these errors were encountered: