Running TypeScript scripts still requires CI-specific workarounds
TypeScript developers writing GitHub Actions scripts report that their workflow does not load TypeScript files directly, so they compile separately or use wrappers and CI-specific switches. Other developers want to run TypeScript without an explicit compile step, though the evidence does not establish how large that market is. The reported 10-minute Angular build is related build friction, but it is a distinct problem from running scripts.
For typeScript developers and GitHub Actions workflow authors. Mentioned from May 2019 to Sep 2026 on Bluesky, GitHub and Hacker News.
5 different people described this problem in 4 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.3/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 4.4/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
Currently, I defer to tsx/tsup/other wrappers + CI switches/overrides to run the ts code for me. Bleeding built-time/actions' constraints into my main code is not acceptable for me
Add typescript support for script files. Is your feature request related to a problem? Please describe. All my source is typescript except for the ones for githup-script. Describe the solution you'd like Add support for loading typescript files.
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks