Nick McCurdy

I'm still experiencing this issue intermittently on version 2.1.24 standalone. It seems to only happen after I alt-tab in and out of the game, but it renders it unplayable until...

Both packages updated with TS 3 support, I'll publish a PR as soon as I have time to test the new version contraints.

It seems like TS 3 is now in master, but there are still peer dependency warnings, see #387.

#387 fixes them. For now you should ignore them until it's merged.

This project uses ts-loader, so it doesn't need Babel. However, there are some features missing from CRA 1 and CRA TS that are now in CRA 2.

I think our most beginner friendly option is to switch back to [CRA's ESLint config](https://github.com/facebook/create-react-app/blob/next/packages/eslint-config-react-app/index.js) with [typescript-eslint-parser](https://github.com/eslint/typescript-eslint-parser). TSLint could potentially be removed if we take this approach, though it could...

Here's my attempt using CRA's ESLint config with TypeScript ESLint Parser: [Replace TSLint with CRA's ESLint config](https://github.com/wmonk/create-react-app-typescript/pull/354)

My pull request disables TSLint but will not error if a config still exists. Do you want full back compatability for existing configs? If so we could keep TSLint enabled...

That's a good point, I think CRA-TS needs a way to allow builds without TS passing. However, I still feel it's best to switch to ESLint for parity with CRA.

If that's a simple non-breaking change, I think we should do it now. However I'm working on removing TSLint anyway, so that would no longer be an issue if my...