-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deno check
does not respect top level exclude
in deno.json
#26864
Comments
|
In my project, the a.js was a typescript file and index.ts imported functions/types from a.js. Perhaps that might be the difference here? |
Interesting; I'm not sure what's causing the difference. I'll temporarily make my project public and share here so the issue is reproducible. |
https://github.com/pmotionf/drivercom-gui Reproduction steps:
|
The components/ui here was not ignored in the "deno check ." case, but instead checked successfully! You can see that the "styled-system" that is also in "exclude" is not ignored. You can compare with "deno check styled-system" |
I can't see Turns out you're right, the problem exists. |
@bartlomieju Is the "needs investigation" tag still applicable here? |
Version: Deno 2.0.6
Running
deno check .
in the project root directory checks files within a directoryfoo/bar
specified inexclude
.deno fmt
anddeno lint
respect theexclude
configuration.Running
deno check foo/bar
wherefoo/bar/
is the excluded directory will return a warning that no matching files were found.TLDR:
foo/bar/
in top levelexclude
indeno.json
deno check .
reports errors infoo/bar/baz.ts
deno check foo/bar
returns warning that no matching files were found.The text was updated successfully, but these errors were encountered: