Ray

icon indicating a website link https://mk1.io icon indicating an email [email protected]

icon company @so1ve icon location [object Location] icon location Never say never. @vuejs · @vue-vine · @clercjs

Results 281 comments of Ray

Typescript error when defineComponent is not used on a mixin

This seemed to be a bug in vue core.

Document required node version

PR welcome :)

Typescript v-model defined types missing

This playground hasn't upgraded to volar 2 yet

False ts(6133) error message

A "minimal" reproduction: https://play.vuejs.org/#eNp9kTFPwzAQhf+KdawlGbqVFAlQBxgAAaOXkF5CimNb9jlEqvLfOTskgFTYnPe+u7xnH+HK2qwPCBsofOVaS8IjBStUqZutBPISLqWTujLak6iNEVtBLuBFFIt8mklEEgg7q0rCpAhR3JjOfp35a3ZFf97WcTsvkiDO4tr8JIbK48QyE9HX0i1okS/ri/zXn2HFyTly3TbZwRvN9Y5xQkLFE61C92Cp5UoSNiI50SuVMh93SYvJVrNevWH1fkI/+CFqEh4denQ9d1k8Kl2DNNm753sc+LyYndkHxfQ/5hN6o0LMOGHXQe859g8upb3trHHU6ubF7wZC7edS6WqZHBMvgd84XtZf1b/jrrN1mpN6hPETGbyzIA==

False ts(6133) error message

Reverting to 1.8.7 does not solve this problem :(

False ts(6133) error message

Interesting, when volar parses the code, the AST node of the second slot is totally lost!

TS service crashes repeatedly

@Mobius0526 `match undefined`: https://github.com/vuejs/language-tools/issues/4457#issuecomment-2163968359

`defineProps` is unable to parse the types generated from `ExtractPropTypes`

Try [`@vue.ts/complex-types`](https://github.com/so1ve/vue.ts/tree/main/packages/complex-types)

`defineProps` is unable to parse the types generated from `ExtractPropTypes`

@sadeghbarati Svelte doesn't "resolve" types to runtime props actually - these type definitions are only used for IDE usage, and they don't affect runtime behavior. But vue needs them to...

`defineProps` is unable to parse the types generated from `ExtractPropTypes`

> Yeah so this issue is really starting to bug me. The compiler just randomly fails on components that use an extend for weeks. I change a completely different component...