ESLint is TypeScript biased--not recognizing respecting config file for ReactJS

[che-wf]

The description is misleading by suggesting "JavaScript and TypeScript". ESLint doesn't accurately recognize that the code is using jsx and not ts. I'm getting error specific to TypeScript that do not pertain to ReactJS. It would be better if the description specified only TypeScript or Diagnostics recognized jsx language and only called errors for React styles.

[Arcanemagus]

I think you mean the TypeScript compiler. ESLint has nothing to do with this package.

You can find a similar issue to what you are seeing in #19 related to flow style type definitions. This package only supports the base, standard, Javascript. Meaning no extensions on top of it.

[damieng]

Can you provide actual screenshots, repro steps and exact error messages?

[che-wf]

Ah! I see what you're saying. Yes, I'm getting ts errors in my plain JS file. I was also seeing ESLint errors when I had the plugin enabled that I wasn't getting from my other ESLinting package. But that's another issue. See example in attached image.

[damieng]

I think what you're actually seeing there is that the version of underlying typescript server doesn't support import etc. yet.

We need to get that updated.

[nemo]

Ditto ^. I'm getting a lot of errors on jsx files (which I guess has nothing to do with them being jsx) for imports and class decorators.

[chee]

i'm running into this with code using the stage 3 class fields proposal and code using stage 3 dynamic import.

dynamic import seems to exist in typescript now, microsoft/TypeScript#16281

and i was sure class fields / member properties already did

ps: the title of this issue should probably change as it is inaccurate and also bizarrely combative

[chee]

oh the class fields thing was a false alarm caused by a dynamic import confusing and frightening typescript further up the file

[damieng]

@chee those features are in TypeScript 2.5 - we're currently locked to 2.4 as that's what the underlying language server does. It's being tracked at sourcegraph/javascript-typescript-langserver#359

[che-wf]

@chee "bizarrely combative"? Not really. Assuming and misguided? Quite possibly.

Do you suggest a better title?

[chee]

@jbcoder that was probably just my reading of it because i hadn't had any lunch and i am frightened of capital letters

[damieng]

Should be fixed with the new ide-typescript 0.8.0 update.