This repository has been archived by the owner on Sep 28, 2020. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 121
Cache option blocks configFile option #171
Comments
This does not make any sense. Objects are not ordered in JavaScript anyway. |
Closing to due to lack of feedback. |
This is truely happened and exausted my several hours。Some attention should be paid here.
|
Please reopen an issue if necessary, with all the details you can as nobody that actually use this loader is maintaining it. I do the bare minimum but not even use it for months... |
I can confirm that this is still an issue, although I'm not sure if the order of the cache property has anything to do with it. If I define configFile and cache is set to true, the configFile is not used. If I comment out cache: true, then the configFile is used. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Cache option is upper then configFile. Webpack rule doesnt use config file (tested with global eslint variable):
If cache option is lower then configFile is loaded but eslint doesnt read rules in
.eslintrc.js
The text was updated successfully, but these errors were encountered: