You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My project is build using external-module pattern and uses a lot of single-exports, but they don't show up in the generated output when I activate "Only exported".
classFoo{// ...}export=Foo;
When I disable "Only exported" I see them as expected.
The text was updated successfully, but these errors were encountered:
This is a difficult one. TypeScript does not mark the class as beeing exported.
I've looked through the code generation of TypeScript and it looks like the only way to detect those single exports is via the AST. I've added a new handler that parses the AST of dynamic modules and manually sets the exported flag.
However I'm not sure whether this covers all cases. As far I can see you can only export top level declarations. If that's the case the solution should be sufficient.
My project is build using external-module pattern and uses a lot of single-exports, but they don't show up in the generated output when I activate "Only exported".
When I disable "Only exported" I see them as expected.
The text was updated successfully, but these errors were encountered: