-
Notifications
You must be signed in to change notification settings - Fork 4
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
Map react component names #6
Comments
Oops yeah moving those components into a standalone package seems to have borked this, I'll get it fixed back up! |
Bleh, that didn't work. It looks like NextJS still munges these names. |
I tried rolling back to this commit where we were using webpack-react-component-name before moving to yarn workspaces since I thought that might be causing issues, but it looks like no matter what I do it keeps throwing this error when trying to build: I also tried the usual |
It'd be great if the React component names were mapped. We used to do this with the babelrc file, but it looks like
tsup
does not support it.Here's what react devtools looks like in dev vs prod
The text was updated successfully, but these errors were encountered: