Replies: 1 comment 3 replies
-
It's vue's behavior - if the component is not resolved, it will render a |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is of course a runtime error, but
vue-tsc
does not raise an error even though it knows the component is not defined (it has type unknown when I hover it).I found the eslint rule
vue/no-undef-components
but it is pretty limited and doesn't work with global componentsWhy doesn't vue-tsc disallow
unknown
tags/components? Is there an option that I'm missing?Beta Was this translation helpful? Give feedback.
All reactions