Ori Livni

it's not exactly related to jshint. you can try install it globally (`npm install -g jshint`). if it doesn't work, you need to edit `PATH` variable of `cmd`

But it means you need all your project made by relative units, which isn't the best case for every site (maybe when IE8 will die). But the option to choose...

It's true that IE 8 doesn't support media queries. But supporting IE 8 means you will probably need to declare twice `font- size` which makes thing more complicated and more...

There is no goal of backward compatibility in the Foundation project. If you'll get to their site with IE 8, you wouldn't be able to see most of the content....

So it seems, we can't do the same conversion 😑 because `Parameters` and `ReturnType` don't work with `Function`. The other question is should we at least replace `any` with `unknown`...

It seems also `unknown` has some issues, I wonder if there is any TS wizard that can solve this issue, if it's possible

Hey @chriskrycho I have the same issue, but I didn't understand the solution. I've also tried to ask in Discord, but no response there

Why saying so? I use https://github.com/bradzacher/eslint-plugin-typescript at work and it works great

@gajus More to this compare: - A rule like `use-flow-type` isn't relevant to TS - There is a rule of `valid-syntax` which is overcome a Babylon bug. Not related to...

@niieani I'm not sure, "const enums" should be mentions, because time after time the TS team against using it in every issue arise about them