From 4c6a57dd3309352a5dc63073877cded4ef7f734a Mon Sep 17 00:00:00 2001 From: sacrosanctic Date: Thu, 4 Jul 2024 05:16:41 +0800 Subject: [PATCH] docs: rephrase a paragraph (#797) --- docs/guide/key-concepts/auto-imports.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/guide/key-concepts/auto-imports.md b/docs/guide/key-concepts/auto-imports.md index 44408947..ecc29c97 100644 --- a/docs/guide/key-concepts/auto-imports.md +++ b/docs/guide/key-concepts/auto-imports.md @@ -79,9 +79,7 @@ export default defineConfig({ ## ESLint -By default, ESLint thinks auto-imported variables are not defined. You have to add them to the `globals` config so it knows these variables exist at runtime. - -WXT generates a config file containing the globals you can extend! By default, WXT will attempt to detect if ESLint is installed in your project and generate the config file if so. If the config file isn't being generated automatically, you can manually tell WXT to generate it: +ESLint doesn't know about the auto-imported variables unless they are explicitly defined in the `globals` config. By default, WXT will generate the config if it detects ESLint is installed in your project. If the config isn't generated automatically, you can manually tell WXT to generate it. ```ts // wxt.config.ts