Hacker News Reader

Comment by no_wizard | Hacker News Reader

Eventually I wonder if the TypeScript team will revert their stance on not allowing compiler plugins. It seems like such a waste not to have a standard package interface. All this is doing is exposing the already provided compiler tools, its not using Babel or anything, its just a nicer API over the raw TS compiler API.

Arguably, the TypeScript team should be supplying that nicer API. Its the only thing missing to me from TypeScript that it really needs.

View on HN

I personally understand the TS team’s stance. Imagine every dev shop having their own TS transforms in the pipeline… I could easily envision fragmentation. TS is great because of how predictable it is.

I don't know. With the plethora of compiler flags that TSC has that can dramatically alter how TypeScript works and where and when it looks for type definitions, I don't think one can really say that cross-project TypeScript setups are predictable. At least, I know I have spent many, many hours playing whack-a-mole with this page (https://www.typescriptlang.org/docs/handbook/compiler-option...) while trying to get various projects integrated with mine.

It's also concerning just how much TypeScript has in it that is specific to just JSX. I mean, how did it work out that React got to get special treatment with the TS compiler? Can any source transforming project get that kind of treatment? That's exactly the sort of thing that should have been delegated to plugins.

React isn’t the only library using JSX, first, and then it’s also true React is the biggest web framework and TS applies best to writing web apps, second, so it seems pretty natural to me they would bake in JSX support.

I suggest you just find one TSConfig setup that works for you and go from that… I’ve never felt these integration pains in the 4 years of heavy TS usage. That said, I authored my own component library, so maybe that’s a factor

That has already happened, but the libraries are being utilized at runtime with associated overheads, and in fact the hoops jumped through are larger and uglier than if TS had plugins.

There is no bloody reason why a custom JSON.parse shouldn't be able to look at compile time at what the expected type of a JSON blog is and compile time generate validation code.

Your example already exists, it’s called TSON, unless you are complaining about how they had to implement that

I also disagree that type validators like Zod/io-ts would benefit from plugins, they are just js code in the end that does defensive checks for you. Unless you have something else in mind

Maybe comment or check out https://github.com/microsoft/TypeScript/issues/54276 that proposes transformer plugins?

This can be easily solved by using https://github.com/cevek/ttypescript, which enables the use of transformers in tsc and allows them to be defined in the tsconfig.json file.

Reply on news.ycombinator.com