Type error when using traditional `defineProps` about unplugin-vue2-script-setup HOT 4 CLOSED

I have tried many way to workaround it, but it seems like the global types injection from @vue/runtime-dom can not be override by another module.

A current workaround:

<script setup lang="ts">
-import { PropType } from '@vue/composition-api'
+import type { PropType } from '@vue/runtime-core'

const props = defineProps({
  value: {
    type: Object as PropType<Record<string, boolean>>,
  },
})
</script>

Remember to use import type to remain it on type level without leaking to runtime

from unplugin-vue2-script-setup.

What's props.any here console.log(props.any)?

from unplugin-vue2-script-setup.

Emmm, typo

<template>
  <div></div>
</template>

<script setup lang="ts">
import { PropType } from '@vue/composition-api';

const props = defineProps({
  value: {
    type: Object as PropType<Record<string, boolean>>,
  },
});

type Value = typeof props.value;
// type Value = {
//     type: PropType<Record<string, boolean>>;
// } | undefined

console.log(props.value!.any);
// 类型“{ type: PropType<Record<string, boolean>>; }”上不存在属性“any”。ts(2339)

</script>

from unplugin-vue2-script-setup.

What happens if you try to separate the type instead

type ValueType = Record<string, boolean>

const props = defineProps({
  value: {
    type: Object as PropType<ValueType>,
  },
});

The weird thing is if you put it inline like your code, it infers the type key lol

But if you put Record<any, any>, I think it behaves fine?

from unplugin-vue2-script-setup.