-
Notifications
You must be signed in to change notification settings - Fork 35
Does this plugin work for Babel@7 & FunctionalComponents? #9
Comments
No, but this does. https://babeljs.io/docs/en/babel-plugin-transform-react-display-name |
@gajus -- the documentation for that one doesn't look like it supports Functional Components -- is that true? |
You are right. Come to think about it, I cannot think of how this could be implemented. |
To be honest, I'd be fine with a transform that attaches |
Any update on this? I would be happy to work on dev for a plugin that does work in v7, but don't want to duplicate work if such a thing already exists. Would be very grateful for any tips/advice. |
It looks like I have sometime ago released a plugin to solve this problem. |
@gajus Yes, but that only covers |
Good point. I haven't touched that code for a long time. https://github.com/gajus/babel-plugin-transform-export-default-name This would work for default exports, though. |
Okay, that's good reference to have. My particular use case requires use of named exports. Are you aware of any way of statically determining the return type of a function (eg jsx) within a Babel plugin? If that's possible, it should be pretty straightforward to loop over all exports and append |
I am not. I don't think that is possible either (accurately), unless you are using strict types (like Flow or TS). |
We went to babel7 a while ago, but we're just starting to use FunctionalComponents much more heavily, and as a result we're starting to see more
<Unknown>
in our component tree.The text was updated successfully, but these errors were encountered: