Feature Request Checklist
Overview
Node.js has native type stripping (i.e. TypeScript file running) now. Yay! https://nodejs.org/en/learn/typescript/run-natively
GitHub Actions created with create-typescript-app -e.g. https://github.com/JoshuaKGoldberg/OctoGuide- currently use blockNcc to use @vercel/ncc for building. They check in their dist/ directory with built outputs. But now that GitHub Actions runners support Node.js versions with TS syntax support, we can do away with that and have the actions just ship their src/ directory with .ts file sources.
Additional Info
I'm not sure what the exact proof of this is. But I've heard of people doing it. Maybe it's that https://github.com/actions/setup-node?tab=readme-ov-file#breaking-changes-in-v5 notes:
Upgraded action from node20 to node24.
🎁
Feature Request Checklist
mainbranch of the repository.Overview
Node.js has native type stripping (i.e. TypeScript file running) now. Yay! https://nodejs.org/en/learn/typescript/run-natively
GitHub Actions created with create-typescript-app -e.g. https://github.com/JoshuaKGoldberg/OctoGuide- currently use
blockNccto use@vercel/nccfor building. They check in theirdist/directory with built outputs. But now that GitHub Actions runners support Node.js versions with TS syntax support, we can do away with that and have the actions just ship theirsrc/directory with.tsfile sources.Additional Info
I'm not sure what the exact proof of this is. But I've heard of people doing it. Maybe it's that https://github.com/actions/setup-node?tab=readme-ov-file#breaking-changes-in-v5 notes:
🎁