Daniel Tschinder

Even if we fix this one file, there are more issues in order to get stuff working in IE11. For example docusaurus ships template strings in some files which get...

Thanks for reporting. I will need to investigate, as we do not use "fs" directly in react-docgen and babel should correctly mock it away already. Anyway I will check.

If I understand this correctly this is somewhat related to #352 but not for importing types but importing complete Components?

There are two problems in this example: 1. React.memo() was not supported, will be fixed in #343 2. The component does not return jsx as felix mentioned and is therefore...

Thanks for reporting this. I'm on your side and think that running the parser on different OS should trigger the same output. I will have a look. It might be...

Can you please provide an example of a component, which shows this behavior?

> Hi, it seems that maybe progress against 6.0 might have stalled out? Is there maybe a reduced set of features/changes which could constitute a 6.0 release, so that it...

A quick update: I tried splitting up the first task but it somehow is all pretty intertwined. - Switching to `babel` from `ast-types` but not yet changing to a _non-estree-AST_...

Do you have an example? We currently supply the parse method to handlers, resolvers as the last argument. Adding the whole ast-types package there would be a little bit risky...

The error is only thrown in `findExportedComponentDefinition`, so if you change the resolver it should not throw. That means either the resolver option does not work, or something else is...