eslintcache not updated after fixing linting issues

[NicolasRannou]

Hi,

I recently migrated an old version of my project to CRA4.

Somehow eslint doesn't work as expected when I open the project with yarn start.

I am using Typescript.

1* yarn start
2* Add a linting error
3* Save
4* Auto-reload recompiles the app but not warning appears in the dev console where VS Studio picked up the issue.

I can not share the source code unfortunately but I'm wondering if somehow the eslintcache can not be overwritten.

If after saving the source code I stop the dev server then remove .eslintcache the error is well displayed next time I restart the dev server. After fixing the error and auto-reload the 'dev server' doesn't pick up that the error was fixed.

package.json

...
    "react-scripts": "4.0.1",
...
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest",
      "prettier"
    ]
  },

TSConfig

{
"extends": "../../tsconfig.base.json",
"compilerOptions": {
  "lib": ["dom", "dom.iterable", "scripthost", "esnext", "es2020"],
  "allowJs": false,
  "skipLibCheck": false,
  "esModuleInterop": true,
  "strict": true,
  "forceConsistentCasingInFileNames": true,
  "noFallthroughCasesInSwitch": true,
  "resolveJsonModule": true,
  "isolatedModules": true,
  "noEmit": true,
  "rootDir": "src",
  "outDir": "build/dist"
},
"include": ["src"],
"exclude": ["node_modules", "build", "scripts", "acceptance-tests", "webpack", "jest"]
}

TSConfig base

{
  "compilerOptions": {
    "module": "esnext",
    "target": "es2020",
    "lib": ["dom", "dom.iterable", "scripthost", "es2020", "esnext"],
    "sourceMap": true,
    "jsx": "react-jsx",
    "moduleResolution": "node",
    "forceConsistentCasingInFileNames": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "suppressImplicitAnyIndexErrors": true,
    "noUnusedLocals": true,
    "allowSyntheticDefaultImports": true,
    "resolveJsonModule": true
  }
}

[NicolasRannou]

Also maybe there is some time out / compilation issue but I have no clue how we can log more information with 'yarn start'.