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
I can reproduce this issue when running this plugin on its own. Other plugins, such as node-resolve are known to cause issues.
I am running this plugin on .d.ts files generated by TypeScript. The plugin can consume .ts and even .js files (with allowJs: true), but this is known to cause issues.
This issue is not related to rolling up @types. The plugin ignores these by default, unless respectExternal is set. @types can contain hand-crafted code which is known to cause issues.
Ah, no. I was debugging it but it didn't pan out. I end up just patching the types package that was breaking stuff for me.
No sweat, that was my first thought too, leveraging something like ts-morph. I'm also debating outputting the raw DTS files from TSC, and then updating the current rollup'd DTS file to export * from there as they're correct. Appreciate your quick response.
Checklist
Other plugins, such as
node-resolve
are known to cause issues..d.ts
files generated by TypeScript.The plugin can consume
.ts
and even.js
files (withallowJs: true
), but this is known to cause issues.@types
.The plugin ignores these by default, unless
respectExternal
is set.@types
can contain hand-crafted code which is known to cause issues.Code Snippet
Actual Output
Expected Output
Additional Context
It works if I alias my class as a type instead:
Output
The text was updated successfully, but these errors were encountered: