-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Futute + Perfomance #143
Comments
@alexander-akait your opinion is always welcome 😄 |
We can introduce special options - addinonalGlobs and pass them to eslint so developer can add files outside the graph
Sometimes you need to ignore some files related to build, but lint them normally, it is very exotic usage,
Yep, we need to improve multi threading API on webpack side and avoid to recreate threads /cc @vankop |
This begs the question "What is the purpose" of this plugin... I'm getting the sense that it has multiple reasons for multiple people. The "goal" of this project should be solidified before making these kinds of back/forth algorithm changes. This plugin provides lint errors for (pick one):
🎉 Having webpack handle threads instead sounds like the real solution. It always bugged me that plugins have to handle that and deal with serialization and such on their own.😊 |
I was analyzing this plugin and doing some performance tests and I realized that some things should be refactored.
Some proposed changes:
1. Not only parse files on graph
.d.ts
are not linted Some files are ignored #120.eslintignore
2. Remove option
exclude
.eslintignore
3. Remove option
threads
The text was updated successfully, but these errors were encountered: