Saad Quadri

For example, if the user had: **.lyntrc** ```json { "react": false } ``` And then ran `lynt --react`, the value of the `react` option should be `true`.

It would be nice to be able to run ``` lynt --watch ``` And to have it automatically update with lint errors whenever files change instead of needing to use...

Lynt v1

1

A [`Lynt v1` milestone](https://github.com/saadq/lynt/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Lynt+v1%22) exists so you can see which issues need to be resolved before releasing v1. The main priority right now: 1. Use ESLint instead of TSLint for...

Now that hooks are in a stable release of React, this plugin should be added to the react lint config. More info: https://reactjs.org/blog/2019/02/06/react-v16.8.0.html#tooling-support

--strict mode

1

Before releasing v1, I am thinking about making lynt's rules a lot more relaxed and to truly only check for errors (this would be using @suchipi's `eslint-config-unobtrusive` which I had...

Editor plugins

4

Currently, there are no editor plugins :( Need to look into how to create these for VSCode, Atom, Vim, etc

Vue support

2

Would be nice to have a `--vue` flag. This shouldn't be problematic on the ESLint side of things due to [eslint-plugin-vue](https://github.com/vuejs/eslint-plugin-vue). Unfortunately, I'm not sure if this can be handled...

Instead of the user needing to pass `--react`, `--typescript`, or `--flow` flags to `lynt`, I could detect this automatically. * Add React support/rules if the user has `react` in their...

TSLint version >= 2.9 seems to have [deprecated `no-unused-variable`](https://github.com/palantir/tslint/pull/3919). > ...the changes in 2.9 make it much more complex for this rule to work as intended, especially with respect to...