Generate type declarations during `bun build`
### What is the problem this feature would solve? I'd like to build my library written in typescript with `bun build` (both for dev and prod), but there's no point in doing so if I or my library's users won't have type declarations. I am developing this library in the ecosystem of other projects, so often it looks like `npm run dev:my-library && npm run dev:my-frontend`. This is a common pattern for developing in monorepos. My current solution is `tsc`, which is slow in watch mode and has its drawbacks. ### What is the feature you are proposing to solve the problem? `--type-declarations` flag for `build` command to generate types along with js files. ### What alternatives have you considered? I see no workaround.
Posted by kynnyhsap on Sep 12, 2023, 7:19 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Generate type declarations during `bun build`
### What is the problem this feature would solve? I'd like to build my library written in typescript with `bun build` (both for dev and prod), but there's no point in doing so if I or my library's users won't have type declarations. I am developing this library in the ecosystem of other projects, so often it looks like `npm run dev:my-library && npm run dev:my-frontend`. This is a common pattern for developing in monorepos. My current solution is `tsc`, which is slow in watch mode and has its drawbacks. ### What is the feature you are proposing to solve the problem? `--type-declarations` flag for `build` command to generate types along with js files. ### What alternatives have you considered? I see no workaround.
Comments (0)
No comments yet. Start the discussion.