Roadmap v1.0.0:

[alexander-akait]

/cc @ricardogobbosouza What is status? Do we have roadmap? I began to receive questions about what to use a plugin or loader, and frankly I do not know what to get 😄

[ricardogobbosouza]

Hi @evilebottnawi

Roadmap v1.0.0:

• Migrate on github actions
• Deprecated node 8
• Support typescript (feat: support typescript #8)

About plugin

Well, the plugin came to solve some problems:

• Cache with cache-loader (errors not shown after starting webpack dev server after initial start webpack-contrib/eslint-loader#267)
• Cache doesn't bust when .eslintrc changes (Cache doesn't bust when .eslintrc changes webpack-contrib/eslint-loader#214)
• Generate an output report (Is there a possibility to generate an output report into one file instead of many reports for each inspected file? webpack-contrib/eslint-loader#207)
• Not to mention that we have more control with the plugin

[alexander-akait]

@ricardogobbosouza Glad to hear it, any ETA?

[alexander-akait]

Migrate on github actions

I will do it 👍

[alexander-akait]

Done github actions 👍

[ricardogobbosouza]

@ricardogobbosouza Glad to hear it, any ETA?

Coming soon...
I intend until the weekend =)

[ricardogobbosouza]

@evilebottnawi What is your recommendation for adding support to typescript?

1. Add type definition file index.d.ts inside repo
2. Create repository @types/eslint-webpack-plugin

[alexander-akait]

We use typescript JSDocs in some repos and generate types inside repo, for example https://github.com/webpack/schema-utils/blob/master/package.json#L23, you can do same

[ricardogobbosouza]

Hi @evilebottnawi
Release v1.0.0
I added a little comparison with the loader

[alexander-akait]

@ricardogobbosouza Can we deprecate eslint-loader in favor this plugin?

[ricardogobbosouza]

@evilebottnawi Theoretically, yes, I have doubts, because many people use the eslint-loader

[ricardogobbosouza]

@evilebottnawi I think we should recommend using this plug-in and warn that the eslint-loader will be depreciated at the end of the year, what do you think?

[alexander-akait]

@ricardogobbosouza Sounds good, so I suggest do not add deprecation message for npm, only deprecate repo (no fixes or features) with recommendation to migrate on this plugin

[ricardogobbosouza]

@evilebottnawi I'll do it :)