Repository navigation
Expose .d.ts library build support at the plugin layer #104
Description
First, thanks a lot for adding this so quickly after #86.
Now that #101 landed, I wanted to ask whether it might make sense to adjust the naming or docs a bit to make the broader use case more visible.
Right now @oxc-angular/vite sounds very Vite-specific, even though it can now also be used with rolldown / tsdown to generate Angular libraries.
Maybe this is something that could be improved through docs/examples, or maybe through naming that better reflects that it is not only useful in Vite app setups.
The main point is discoverability: people may otherwise not realize that this now also covers library build workflows.
Anyway, thanks for the great work.
Reacted by Sergi Luque
Activity
[-]`@oxc-angular/vite naming feels too Vite-specific for current library build support[/-][+]`@oxc-angular/vite` naming feels too Vite-specific for current library build support[/+]schplitt commentedon Mar 10, 2026
@Brooooooklyn I think I misunderstood at which layer this was implemented.
From looking at #101 again, the change was added at the compiler/API level via
dts_declarations, not as library-build support in the plugin itself.So in that case, I think the follow-up question is slightly different: should there be separate Rollup/Rolldown-oriented plugin support for this, or should this compiler option also be exposed through the existing Vite plugin options where that makes sense?
At least to me, this issue would still be useful as a way to track that tooling/plugin-layer follow-up, since the compiler capability now exists but discoverable end-to-end library build support does not seem fully surfaced yet.
Anyway, thanks again for the great work.
[-]`@oxc-angular/vite` naming feels too Vite-specific for current library build support[/-][+]Expose `.d.ts` library build support at the plugin layer[/+]feat(vite): augment library .d.ts with Ivy type declarations (#104) (#…