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
When I run vue-tsc on our Nuxt project, it clearly fins an error, but then returns successfully, which makes our pre-push hook pass, even though it should fail.
What is expected?
The process to throw when finding errors.
What is actually happening?
The process passes when finding errors.
Link to minimal reproduction
No response
Any additional comments?
Here's a screenshot of what happens:
The text was updated successfully, but these errors were encountered:
I actually think it's just a false positive. getRouteBasename always returns a string, so the assigned value to pageSource is always a string, not sure why it thinks it can be undefined:
So the Vue Language Tools seem to interpret this correctly, just the CLI version of vue-tsc doesn't.
Having a similar issue. npx nuxi typecheck does not give out error code upon errors, so execution continues and i successfully commit not working code.
When trying to run npx vue-tsc, the behavior is as expected (execution halts).
Vue - Official extension or vue-tsc version
vue-tsc 2.2.0
VSCode version
N/A
Vue version
3.5.13
TypeScript version
5.7.3
System Info
package.json dependencies
Steps to reproduce
When I run vue-tsc on our Nuxt project, it clearly fins an error, but then returns successfully, which makes our pre-push hook pass, even though it should fail.
What is expected?
The process to throw when finding errors.
What is actually happening?
The process passes when finding errors.
Link to minimal reproduction
No response
Any additional comments?
Here's a screenshot of what happens:
The text was updated successfully, but these errors were encountered: