-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Enabling fix doesn't seem to update source files #43
Comments
I have the same problem. |
@ricardogobbosouza Can you take a look at this problem? Thank you. |
I have the same problem.
|
Same problem here, what's the latest? Node 15.0.1 |
Hello, It is still not fixed. |
sakura-flutter
added a commit
to sakura-flutter/tampermonkey-scripts
that referenced
this issue
Dec 1, 2020
@4版本兼容webpack@5与webpack-cli@4 eslint-webpack-plugin必须要2.4.1版本以上,[之前的版本传递fix选项失败](webpack-contrib/eslint-webpack-plugin#43)
sakura-flutter
added a commit
to sakura-flutter/tampermonkey-scripts
that referenced
this issue
Aug 1, 2022
@4版本兼容webpack@5与webpack-cli@4 eslint-webpack-plugin必须要2.4.1版本以上,[之前的版本传递fix选项失败](webpack-contrib/eslint-webpack-plugin#43)
sakura-flutter
added a commit
to sakura-flutter/tampermonkey-scripts
that referenced
this issue
Aug 1, 2022
@4版本兼容webpack@5与webpack-cli@4 eslint-webpack-plugin必须要2.4.1版本以上,[之前的版本传递fix选项失败](webpack-contrib/eslint-webpack-plugin#43)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
Running webpack with the fix option enabled should update the source code and autofix the rules that it can.
Actual Behavior
If running without the fix option, it shows the error. If running with the fix option enabled, no errors are shown but source code is not updated.
Code
How Do We Reproduce?
With configs above, running npx webpack in theory should fix the following file by re-ordering the imports:
The text was updated successfully, but these errors were encountered: