Closed nonara closed 2 years ago
Definitely in favor of having one tool for adding additional, pluggable features to TS. I started brainstorming in https://github.com/cspotcode/hookable-typescript but never had time to go anywhere with it.
I'd also like the option to avoid modifying typescript/tsc/tsserver in situations where other tools in the dependency tree should get access to unmodified copies of tsc. Like how ttsc and tsc can live side-by-side.
I'm also not sure how writing to the filesystem works with yarn2's PnP cache. I believe those zip files are mounted read-only.
Development is underway!
Discussion: https://github.com/nonara/ts-patch/discussions/40 Dev Branch: https://github.com/nonara/ts-patch/tree/v2
Hi all!
I've been thinking about this for awhile, and I thought I'd go ahead and gauge interest.
ttypescript
and to a lesser extent,ts-patch
, have been filling a void for awhile now. I know that they have been very helpful for many of us who needed to do more with the TS compiler. With that said, in hindsight—gauging from personal use and feature requests—I believe that there is room for improvement in our overall design which could make for a much more powerful and perhaps more complete plugin architecture.Update
Given the issues with ttypescript and its unmaintained status and the current limitation with
ts-patch
, I think it's time to do the rewrite.I've sketched out the design. Here are the highlights:
tsc
or something else, default istspc
)ttypescript
style transformer packagesI've decided to keep the name for simplicity and visibility. So the rewrite will be housed in ts-patch v2.
You can follow https://github.com/nonara/ts-patch/discussions/40 for updates