Hi all, I've been using neovim for about 6 months now and really enjoy it, but my only issue is that I find the feedback loop from eslint is incredibly slow - in the seconds range, compared to the same project in vscode. I assume this is an implementation issue on my end, but I have no idea what to do to resolve this.

I've also noticed that in projects that use the typescript-eslint parser, sometimes node processes just go through the roof.. which again is not an issue with whatever vscode is doing.

Thanks in advance for the help!!

So I'm pretty new to Typescript, but at work I'm trying to help TS adoption on our very large project. However, currently the typechecking analysis through Webstorm and VSCode is very slow and I believe its hurting adoption and the general perception of Typescript due to how slow typchecking can be. Often it can it can up to a minute or longer for either IDE to perform its typechecking to show an error or update a reference. I'm wondering if its due to how we have our project set up?

For ease of introduction, my coworkers set up Typescript to rely more on the IDE and the Typescript Language Service, use ESLint (typescript-eslint plugin) instead of TSLint and disable emitting/compilation.

Here's our tsconfig. Do we have something setup incorrectly? Or is TS generally just slow on large projects? Thanks

{
  "compilerOptions": {
    "target": "esnext",
    "moduleResolution": "node",
    "allowJs": true,
    "noEmit": true,
    "strict": true,
    "module": "esnext",
    "isolatedModules": false,
    "esModuleInterop": true,
    "resolveJsonModule": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "preserveConstEnums": true,
    "removeComments": false,
    "lib": ["esnext", "dom"],
    "baseUrl": ".",
    "paths": {
      // ...
    },
    "experimentalDecorators": true,
    "disableSizeLimit": true,
    "jsx": "react",
    "types": ["node", "jest"]
  },
  "include": [
    "src/**/*",
  ],
  "exclude": [
    "dist/**/*",
    "node_modules/**/*",
  ]
}