oleks/wxt
1
0
Fork 0
Code Issues Pull Requests Actions 112 Packages Projects Releases Wiki Activity

docs: rephrase a paragraph (#797)

Browse Source
This commit is contained in:
sacrosanctic
2024-07-04 05:16:41 +08:00
committed by GitHub
parent 3ce8c8b1f4
commit 4c6a57dd33
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide/key-concepts/auto-imports.md
+1 -3
View File
@@ -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