logoalt Hacker News

mschuster91 • today at 2:34 PM • 2 replies • view on HN

> Typescript rewrote its compiler in Go, but that doesn't affect which runtime you use for the resulting Javascript code.

It unfortunately has other implications, ts-loader (used by webpack) for example is not compatible with the new Go crap so you need to do weird pinning down to v6 to get your builds working again [1].

[1] https://github.com/TypeStrong/ts-loader/issues/1671


Replies

jerf • today at 2:56 PM

Yes, everything I have is pinned that way too. That's why I said "when it is done", even in my limited experience and contact with TS it is not currently a suitable replacement, and I'm not a particularly hard user of the tool chain. (I am having a hard time phrasing this in a way that I'm completely sure can't be potentially read as snarky or short-tempered, so I guess I'll just go with the clumsy direct statement that I'm agreeing with you and continuing the thought from my own experience, not trying to disagree.)

As near as I can see, it isn't anything fundamental to the rewrite, it's just a transitional phase, though.

gen2brain • today at 2:43 PM

Well, that "Go crap" needs some explanation. The reason I am not involved in JS is because I mostly use Go for backend, and I am happy I have no relation with frontend at all. And even that is just small part of my job and what I do daily (Radius, Diameter, etc.). But, I never heard about Go crap (in that context maybe), or experienced any crap there, it is just nice and simple. What are the issues?

➕ show 1 reply