typescript-eslint-parser

I went through a similar process and chose TS > Flow. - Renaming to .ts and .tsx is nicer than adding comments, because it integrates better with tooling (compile all files that end with .ts) and it's easier to see at a glance what's ported - You can always compile TS to ES2018 and run that through Babel, if you like. TSLint -> ESLint is indeed a change, though you can continue to use most of ESLint for TS [0] - As a rule, TS is compile time only. There are a few exceptions, but that's almost always the case. For me the advantages of TS are: - Huge library of community written typings for JS libs - Mapped types - Full support for literal types - Read only types That said, I really like Flow's co/contravariance annotations, and the corresponding $Supertype and $Subtype functions. That, and nominal typing can be really convenient (coming to

Hi Alex (I have an email from you that I have to respond to)! TS guy here. We've had discussions around this and the reason we use our own AST format is for compilation speed and editing scenarios, both of which our team really focuses on. I'll also note that incredible folks like James Henry have already written tools to convert TypeScript ASTs to the ESTree format[1]. I've heard it's been working well for using ESLint on TypeScript code. [1]: https://github.com/eslint/typescript-eslint-parser

The author recommends grabbing jQuery where necessary and I'd have to disagree. Instead they could look into ngOnChanges in the component lifecycle or using a different ChangeDetectionStrategy on the component. But maybe jquery is the better option for their use case. We're using it for an internal app at walmartlabs and its been great coming from angular 1. Working with angular-cli today is very stable and fully featured. I published a quick test module yesterday using angular-cli https://scttcper.github.io/ng2-adsense/ after gzip its small even with all of bootstrap v4's css included. It sounds like with ahead of time compilation we could see even faster first paint times combined with lazy loading of routes and modules it should be very fast even without using angular universal. Typescript is good, but I don't like tslint. I'm excited