typescript-eslint · cseas · Jul 8, 2025 · Jul 23, 2025 · Jul 23, 2025 · Aug 1, 2025
diff --git a/.gitattributes b/.gitattributes
@@ -1,6 +1,4 @@
 * text=auto eol=lf
 
-# force github to treat out custom jest snapshot extension as normal jest snapshots
-*.shot linguist-language=Jest-Snapshot
 *.shot linguist-generated
 packages/scope-manager/src/lib/**/* linguist-generated
diff --git a/.github/workflows/nx-migrate.yml b/.github/workflows/nx-migrate.yml
@@ -2,7 +2,7 @@
 # `nx migrate` when renovate opens a PR to change the version of @nx/workspace.
 #
 # You will therefore also notice that in the renovate configuration, we ignore any packages which
-# Nx will manage for us as part of `nx migrate` such as the remaining @nx/* packages and jest.
+# Nx will manage for us as part of `nx migrate` such as the remaining @nx/* packages.
 
 name: Nx Migrate
 

diff --git a/.vscode/extensions.json b/.vscode/extensions.json
@@ -5,7 +5,6 @@
       "editorconfig.editorconfig",
       "esbenp.prettier-vscode",
       "streetsidesoftware.code-spell-checker",
-      "tlent.jest-snapshot-language-support",
       "mrmlnc.vscode-json5",
       "vitest.explorer"
   ],

diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -20,19 +20,5 @@
   "javascript.preferences.quoteStyle": "single",
   "typescript.preferences.quoteStyle": "single",
   "editor.defaultFormatter": "esbenp.prettier-vscode",
-
-  // make the .shot files from jest-specific-snapshot act like normal snapshots
-  "files.associations": {
-    "*.shot": "jest-snapshot"
-  },
-  "vsicons.associations.files": [
-    {
-        "icon": "jest_snapshot",
-        "extensions": [
-            ".shot",
-        ],
-        "extends": "jest_snapshot"
-    },
-  ],
   "nxConsole.generateAiAgentRules": true,
 }
diff --git a/docs/contributing/Pull_Requests.mdx b/docs/contributing/Pull_Requests.mdx
@@ -48,16 +48,6 @@ For rule tests we recommend, when reasonable:
 
 AST tests belong in the `ast-spec` package, within `fixtures/` subfolders alongside the AST declarations. Each test has its own `<test-name>/` folder, containing a `fixture.ts` file defining the test, and a `snapshots/` subfolder. Happy-path test folders are stored directly under `fixtures/`; error-path test folders go under `fixtures/_errors/`. You can check out the [`ClassDeclaration` fixtures folder](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/ast-spec/src/declaration/ClassDeclaration/fixtures) for an example of both happy-path and unhappy-path test folders.
 
-### Updating Snapshots
-
-[Jest snapshots](https://jestjs.io/docs/snapshot-testing) are generated for use in some tests, e.g. for [rule schemas](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin/tests/schema-snapshots) and [code examples in rule docs](https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin/tests/docs-eslint-output-snapshots). You may need to re-generate these snapshots after adjusting a rule and/or its documentation, by running the relevant test suite(s) with the `-u` flag:
-
-```bash
-cd packages/eslint-plugin
-yarn test docs -u
-yarn test schemas -u
-```
-
 ## Raising the PR
 
 Once your changes are ready, you can raise a PR! 🙌

diff --git a/docs/maintenance/Pull_Requests.mdx b/docs/maintenance/Pull_Requests.mdx
@@ -80,7 +80,6 @@ If there's no backing issue:
   - Parenthesis and whitespace (see: `getWrappingFixer`).
   - Unions and intersections (see: `unionConstituents` and `intersectionConstituents`).
 - Unit tests:
-  - All lines are covered per the Codecov / `yarn jest path/to/impacted/file --coverage` report.
   - Both "positive" and "negative" ("valid" and "invalid") cases exist, if reasonably possible to test for.
   - Fixes and suggestions, if present, don't remove `//` or `/*` comments
   - `invalid` lint rule errors include line and column information

diff --git a/packages/scope-manager/tests/eslint-scope/README.md b/packages/scope-manager/tests/eslint-scope/README.md
@@ -6,7 +6,6 @@ The intention is to help us ensure we do not regress functionality compared to t
 They have been modified to:
 
 - be written in TypeScript
-- work with jest
 - work with our folder structure
 - adhere to our formatting and linting style