Both of these cases fail on the parseESLint, as there isn't any try {} catch around parsing and fallback return.
There was already one issue #143 about this, but it was closed due to lack of info. Hope these details will be enough.
Not sure how to fix the file locking which I guess would be the best fix, but even error handling in JSON parsing generally helps to recover from this problem.
Reproduction
It's hard to reproduce as typical race conditions problems. I can't reproduce it locally on my machine. It only happens on the basic GH Actions runner. Maybe that's because of the slower disk and bigger chance of double write or write with read occuring at the same time.
Describe the bug
webpack
+unplugin-auto-import
combination sometimes fail on parsing.eslintrc-auto-import.json
.From quick checks I've managed to find 2 conditions for this error to occur.
Sometimes there are multiple concurrent writes to this file. Then
.eslintrc-auto-import.json
is corrupted.Both of these cases fail on the
parseESLint
, as there isn't anytry {} catch
around parsing and fallback return. There was already one issue #143 about this, but it was closed due to lack of info. Hope these details will be enough.Not sure how to fix the file locking which I guess would be the best fix, but even error handling in JSON parsing generally helps to recover from this problem.
Reproduction
It's hard to reproduce as typical race conditions problems. I can't reproduce it locally on my machine. It only happens on the basic GH Actions runner. Maybe that's because of the slower disk and bigger chance of double write or write with read occuring at the same time.
System Info
Used Package Manager
yarn
Validations