Hacker News new | past | comments | ask | show | jobs | submit login

One of my favorite things about typescript was being able to ditch Babel and eslint and their myriad of requirements to get things that are considered standard. I get why they do it, it's just something I prefer.

Take create-react-app and the now deprecated create-react-app-typescript. The node_modules folder of the CRA app is over a hundred megs bigger than that of CRA-ts, and it doesn't even have feature parity.




Is this still dependent on browser adoption? I recently had to transpile a Typescript library via Babel to JavaScript since Chrome didn’t like the original import statements.


Typescript is not intended to work in browsers without a compile step being involved.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: