From 870d21c1e6d7e21e55a1e316e5bdb83be78054a1 Mon Sep 17 00:00:00 2001 From: Josh Goldberg Date: Wed, 11 Oct 2023 09:17:04 -0400 Subject: [PATCH] docs: mention --trace-deprecation Node flag --- docs/linting/Troubleshooting.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/linting/Troubleshooting.mdx b/docs/linting/Troubleshooting.mdx index fc262847ef3c..847f6ff66bf6 100644 --- a/docs/linting/Troubleshooting.mdx +++ b/docs/linting/Troubleshooting.mdx @@ -333,7 +333,11 @@ Rules such as [`no-unsafe-argument`](/rules/no-unsafe-argument), [`no-unsafe-ass If you're seeing this warning, it's likely you're using an ESLint plugin (or other tooling) that hasn't been updated for typescript-eslint v6. Make sure you're using the latest versions of each of your ESLint plugins (and other tooling). -If you've using many ESLint plugins, have updated each to their latest version, and you're not sure which one this complaint is coming from, try disabling half of them at a time to narrow down which plugin it is. +If you've using many ESLint plugins, have updated each to their latest version, and you're not sure which one this complaint is coming from, try either or both of: + +- Running with [`--trace-deprecation`](https://nodejs.org/api/cli.html#--trace-deprecation) (e.g. `npx crossenv NODE_OPTIONS=--trace-deprecation npm lint`) +- Disabling half of them at a time to narrow down which plugin it is + Then make sure each of those plugins has a GitHub issue asking that they release a version supporting typescript-eslint v6. :::tip