Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Map plugins to transformers and vice versa #8790
Is your feature request related to a problem? Please describe.
You guys have done a fantastic job on babel.
An extension of #6205
I have an issue when I'm dealing with a syntax plugin but don't know its associated transformer plugin and vice versa.
Using plugins listed in stage preset deprecation error message.
Expecting all experimental features to be enabled and configured. But run into:
Look into documentation, and see
I couldn't initially confirm which transformer if any associated with this syntax plugin. Names were changing in the ecma proposals and proposals were being combined as well.
During that point in time I didn't know which situation I was in:
After an hour of researching the ecma repositories and babel github issues and development, I found what I needed: #8130 (comment)
Describe the solution you'd like
Mainly, mimic how proposals are referenced but for the respective feature.
Describe alternatives you've considered
Reference babel's relevant development tracker issue for the relevant feature in progress, in documentation / error messages
Teachability, Documentation, Adoption, Migration Strategy
And similar solution on the transformer documentation (maybe include into error messages referenced in the issue linked at the top of this post too).
There are further improvements we can do that relate to this issue. But for an easy and effective solution now, we can start with linking the transformers and the plugins where we might need to find them.
Hey @andrewmiller1! We really appreciate you taking the time to report an issue. The collaborators