You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`--workspace <path>`| Path to your workspace. All subdirectories except node_modules and those listed in `--ignore` are checked |
56
-
|`--output <human\|human-verbose\|machine>`|
57
-
|`--watch`| Will not exit after one pass but keep watching files for changes and rerun diagnostics |
58
-
|`--tsconfig <path>`| Pass a path to a tsconfig or jsconfig file. The path can be relative to the workspace path or absolute. Doing this means that only files matched by the files/include/exclude pattern of the config file are diagnosed. It also means that errors from TypeScript and JavaScript files are reported. |
59
-
|`--ignore <path1,path2>`| Files/folders to ignore - relative to workspace root, comma-separated, inside quotes. Example: `--ignore "dist,build"`|
60
-
|`--fail-on-warnings`| Will also exit with error code when there are warnings |
61
-
|`--fail-on-hints`| Will also exit with error code when there are hints |
62
-
|`--compiler-warnings <code1:error\|ignore,code2:error\|ignore>`| A list of Svelte compiler warning codes. Each entry defines whether that warning should be ignored or treated as an error. Warnings are comma-separated, between warning code and error level is a colon; all inside quotes. Example: `--compiler-warnings "css-unused-selector:ignore,unused-export-let:error"`|
63
-
|`--diagnostic-sources <js,svelte,css>`| A list of diagnostic sources which should run diagnostics on your code. Possible values are `js` (includes TS), `svelte`, `css`. Comma-separated, inside quotes. By default all are active. Example: `--diagnostic-sources "js,svelte"`|
64
-
|`--threshold <error\|warning>`| Filters the diagnostics to display. `error` will output only errors while `warning` will output warnings and errors. |
65
-
66
-
### FAQ
67
-
68
-
#### Why is there no option to only check specific files (for example only staged files)?
69
-
70
-
`svelte-check` needs to know the whole project to do valid checks. Imagine you alter a component property `export let foo` to `export let bar`, but you don't update any of the component usages. They all have errors now but you would not catch them if you only run checks on changed files.
0 commit comments