Hacker News Reader

No alternative, just the output of TSC with eslint both set to ES2019[0]. But if that's not a good idea, I'd really like to know why. I don't like extra tooling that I don't fully understand just for the heck of it. @WorldMaker has a good point below.

[0] and I just discovered our default boilerplate is using ts set to ES6 and eslint set to ES2019. Facepalm.

View on HN

We still typecheck and build in different steps due to speed; we can build our JS much faster than TS can with Babel + Webpack. We also have a bunch of old custom features that our build system needs to support, so bolting them onto tsc was a non-starter.

Plus, we have to support some fairly old browsers (we only recently dropped support for IE11), so Babel is certainly doing a lot of transforms on the bundles we ship to older browsers.

Separately, do you mean Terser instead of ESLint? ESLint isn’t really part of our build process.

Terser? Sigh... Add that to the list of 200+ tooling options that my team doesn't have time to investigate.

It’s a minifier. I am not sure if tsc minifies your code for you or not, but if it doesn’t, you’d definitely want that in your build step. It’ll shrink your built files considerably, and it’s a pretty standard, uncomplicated tool.

Reply on news.ycombinator.com