prettier-eslint: Error generating `parserServices` for eslint plugin `@typescript-eslint`

@ricardolpd I was able to fix this by adding "project": ["tsconfig.json"],:

"parserOptions": {
  "ecmaVersion": 2020,
  "project": ["tsconfig.json"] ,
  "sourceType": "module"
},

could anyone provide an example of a config that provides a work around for this? We are facing this issue with '@typescript-eslint/require-await' in our mono repo.

update typescript-eslint-parser (Deprecated) to @typescript-eslint/parser

when i use .eslintrc.js with

parser: '@typescript-eslint/parser',
plugins: ['@typescript-eslint'],

I directly remove code

  if ([".ts", ".tsx"].includes(fileExtension)) {
    // XXX: It seems babylon is getting a TypeScript plugin.
    // Should that be used instead?
-    formattingOptions.eslint.parser = require.resolve(
-      "typescript-eslint-parser"
-    );
  }

it works fine

I’m looking into this today.

The main suggestion here seems to be to update from the old typescript-eslint-parser to the new @typescript-eslint/parser.

However, I would like to make another suggestion: make prettier-eslint respect any predefined TS parsers (via an existing parser option in the ESLint RC).

This way, users may use their own version of the TS parser, in much the same way that prettier-eslint allows users to use their own version of ESLint.

@m-cat that didn’t work for me. We are also seeing this trying to add the same require-await rule as @ricardolpd. Are there any other suggestions on how to fix this?

I think this issue has been solved by the release of prettier-eslint v9.0.0.

Adding another solution since I found this thread via google. We also had a monorepo and the necessary parserOptions.project property was set correctly. The stack trace pointed to a jest.config.js file it was trying to lint, I explicitly ignored that file in my .eslintrc.js:

ignorePatterns: ["jest.config.js", "node_modules/", "dist/"],

For me, the issue was that the parserOptions.project was not looking in the current project of a mono-repo. I had to specify it as if it was from the top of the repo.

packages/react-desktop/package.json

  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ],
    "parserOptions": {
      "project": "./react-desktop/tsconfig.json"
    },
    "rules": {
      "@typescript-eslint/strict-boolean-expressions": "error"
    },

I’m not sure if that is a bug or not. It seems strange the . is the repo root, not the current project root. Now I can avoid those pesky falsyness in conditionals.

The requirement for the “parserOptions.project” property was seen after running npx eslint . --ext .ts

Error: Error while loading rule '@typescript-eslint/strict-boolean-expressions': You have used a rule which requires
parserServices to be generated. You must therefore provide a value for the "parserOptions.project" property for
@typescript-eslint/parser.

I have created a quick test repo: https://github.com/r0skar/prettier-eslint-test

If you open it in VSCode with the prettier extension installed, you will get an error upon saving index.ts, but running yarn eslint will not show any error.