-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Keep original component name when building to JS #5154
Comments
These are mapped to hashes in order to avoid name collisions (See parcel-bundler/parcel#6092). I think we could use EDIT: Although I'm not sure |
I think using a hash to avoid name collisions is a good solution, but can we also include the original name in the final result? For example |
Hey guys. We're using |
Would it be feasible to switch from Parcel to Rollup to build the react-spectrum packages? I use Rollup to build tailwind-merge (Rollup config) and it preserves all internal names, only adding small bits to variables that would otherwise clash, keeping them human-readable. |
Provide a general summary of the feature here
It'd be helpful if the name of components shown in React DevTools include the original component name. It'd make it easier for developer to debug their application.
https://syueo.csb.app/
🤔 Expected Behavior?
@react-spectrum
and@react-aria
's components shown in React DevTools has meaningful name.😯 Current Behavior
@react-spectrum
and@react-aria
's components shown in React DevTools has auto-generated name. It's quite difficult to tell what component it is from the name alone.💁 Possible Solution
No response
🔦 Context
I was trying to debug a component created using
@react-aria
's hooks and components, but the name makes it hard for me to distinguish them from each others.💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response
The text was updated successfully, but these errors were encountered: