Closed dko-slapdash closed 2 years ago
The industry won't die. Many projects rely on plugins, including my own. This repo seems not to be maintained anymore, unfortunately. I have access to ts-patch, but not here.
If @cevek wants to add me as a maintainer, I'd be glad to maintain this and hopefully later rewrite and merge the two libraries into a more robust plugin architecture.
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 is tspc
)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 updates here: https://github.com/nonara/ts-patch/discussions/40
Actually, I also thought that the library was already out of date and did not work, 😅 but after testing it on the latest versions of ts
, it turned out that everything is working, the only thing that broke(warning) is some kind of incompatibility with the new version of node module system, but I fixed it, so now everything is in working order.
Actually, I also thought that the library was already out of date and did not work, sweat_smile but after testing it on the latest versions of
ts
, it turned out that everything is working, the only thing that broke(warning) is some kind of incompatibility with the new version of node module system, but I fixed it, so now everything is in working order.
I can verify that I am using this package successfully with typescript 4.4.4 (not updated to 4.5.x yet) for a few months. However, I wasn't using it two years ago so I have no previous behavior to compare to. One barrier that had to be overcome was that the plugin main entry was called repeatedly to engage a lower level of iteration (the transform) in the plugin. Once I figured that out and put in a guard to initialize the plugin only once, all was well. I couldn't find anything about that in the documentation.
Infrequent updating of a package isn't necessarily undesirable, it can be a sign of welcome stability.
Having two separate available and independent approaches, ttypescript
and ts-patch
, is a good thing. Eventually I may try to integrate with ts-patch
as well.
Hi @cevek @nonara,
Been a happy users of ttypescript for almost 2 years. Decided to upgrade TS, and:
What's the future of the project? Or, maybe, the entire industry of TS plugins in dying, and there is no alternative?
Thanks!