`prettier-eslint` command fails due to unknown environment key `jest/globals` about prettier-eslint HOT 4 CLOSED

@tommy-mitchell I had the same issue and what I ended up doing in my .eslintrc.js file

overrides: [
    {
      // enable eslint-plugin-testing-library for matching testing files
      files: ['**/?(*.)+(spec|test).[jt]s?(x)'],
      extends: ['plugin:jest/recommended'],
    },
  ]

from prettier-eslint.

Turns out jest now needs to be @jest in the config. Closing this to open a PR in https://github.com/kentcdodds/eslint-config-kentcdodds.

from prettier-eslint.

Reopening this because the problem still seems to be with prettier-eslint. If I change jest.js in the config to have the @jest/globals key, prettier-eslint works, but then ESLint breaks as it can’t find the new environment key. Removing the @ reverses the problem.

Maybe somehow it’s version mismatch between the two tools? I’m using VSCode extensions for them, which is where the error messages are being reported. I’m on mobile but I can check later.

from prettier-eslint.

Stale issue

from prettier-eslint.