@vitejs/plugin-vue boolean props with no value have wrong type with --mode production and script setup

[hanneskuettner]

Describe the bug

When creating a component with the script setup syntax and a boolean prop and accessing the prop results in different (and wrong) types when running vite --mode production vs vite.

<!-- MyComponent.vue -->
<script setup lang="ts">
    const props = defineProps<{ bool: boolean }>();
    
    console.log(typeof props.bool)
</script>

<!-- App.vue -->
<template>
    <MyComponent :bool="true" />
    <MyComponent bool /> 
    <MyComponent />  
</template>

This results in the following output using vite

boolean
boolean
boolean

and using vite --mode production

boolean
string
undefined

I have verified (see reproduction) that it's only the case for components using the script setup syntax and not the normal script tags.

Reproduction

https://stackblitz.com/edit/vitejs-vite-2ehfh6

Running vite --mode production and vite results in different output.

System Info

System:
    OS: Linux undefined
    CPU: (4) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: Unknown - /bin/jsh
  Binaries:
    Node: 14.16.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /bin/yarn
    npm: 7.17.0 - /bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^1.9.4 => 1.9.4 
    vite: ^2.6.13 => 2.6.14

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[grunghi]

Just stumbled upon this issue and it was apparently resolved in the new release of vue 3, see vuejs/core#4783

[hanneskuettner]

Oh, so it was a vue-next and not a vite problem. Sorry about that, I thought I checked thoroughly enough.

Marking this as closed then, thanks for pointing me to specific issue!