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
fix: use --build
for type-checking to be exhaustive and less-fragile
#274
Conversation
Fixes #267 Thanks @segevfiner for noticing this new feature! Currently there's still a small annoyance that `vue-tsc` would output an extra error message when there're type errors in `.vue` files vuejs/language-tools#2622 But it works well if there's no error. I've already submitted a PR to address it vuejs/language-tools#3176
Actually, they might have changed things so that it does run but doesn't type check packages with Be sure we actually get errors with this. I have requested microsoft/TypeScript#53979 for them to make this work. |
What do you mean by "might have changed things"? I tested this project https://github.com/sodatea/no-emit-test with both 5.0.4 and 5.1.0-dev.20230512, both reporting the same correct number of errors - though in subsequent calls the error location is lost for |
Fixes #267 It's because I moved the `compilerOptions` from `tsconfig.json` to `tsconfig.app.json` in the 2023-05-05 (v3.6.2) release, but forgot to change the `type-check` script. This isn't comprehensive because it doesn't check all the sub-projects, but at least it's the same scope as previous versions. Ideally I hope #274 can work reliably. But now I'm not sure. So let's first fix this bug.
|
I tried configuring this myself once before but got no errors, but maybe I did something wrong or it was a different issue. |
It might have been the |
@cexbrayat This change could help catch the issue in #386 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave it a try, and I think it works well 👍
One note though: all the errors are logged twice. But I'm not sure if this is really an issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like typescript-jsx-nightwatch
is failing when running pnpm test
locally. There is probably a noEmit
to add in another file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
--build
for type-checking to be exaustive and less-fragile--build
for type-checking to be exhaustive and less-fragile
FYI: I think this setting is incompatible with any JS in the project. I have some legacy JS files in my app, so I have allowJS: true. If I try running type checking, I get "js emit is not supported." And if I add |
- 'vue-tsc' uses '--build' because we are using 'references' in tsconfig.json. - 'vue-tsc' doesn't use '--noEmit' because it is incompatible with '--build'. Instead we set 'noEmit' to 'true' in the referenced tsconfig.json files. - 'vue-tsc' uses '--force' to make check-only builds more reliable (see vuejs/create-vue#274).
Fixes #267
Closes #181
Thanks @segevfiner for noticing this new feature!
Currently there's still a small annoyance thatvue-tsc
would output an extra error message when there're type errors in.vue
files vuejs/language-tools#2622 But it works well if there's no error.I've already submitted a PR to address it vuejs/language-tools#3176