script setup: ref imported from a .vue file doesn't work after build

[stephanedemotte]

Version

3.0.4

Reproduction link

https://github.com/stephanedemotte/_issue-vue3-script-setup

Steps to reproduce

Create a fresh vitejs app

helloworld.vue

<template>
  <div>
    HelloWorld [{{ isActiveTpl }}]
  </div>
</template>

<script>
import { ref } from 'vue'
export const isActive = ref(false)
</script>

<script setup>
const isActiveTpl = isActive
</script>

app.vue

<template>
  <div>
    App [{{ isActive }}]
  </div>
</template>

<script setup>
import { isActive } from './components/HelloWorld.vue'
</script>

What is expected?

the value should be: true / false

What is actually happening?

After build the ref variable output a weird value

If i try to do isActive = !isActive on app.vue, i've got no error on dev, but got Error: Illegal reassignment to import 'isActive' when i try to build

---

Builded link
http://test-vue-export.gaidaandsteph.com/

[yyx990803]

Duplicate of #2699 and already fixed by 085bbd5 (not released yet)

[posva]

But wasn't 085bbd5 included in v3.0.4?
The problem here only appears after bundling for prod

[stephanedemotte]

Yep, i've tested after the fix

[CHOYSEN]

Yep, i've tested after the fix

It work fine for me after the fix whether it's dev or build...

[stephanedemotte]

@CHOYSEN if you build my repo you didn't get that ?

[CHOYSEN]

@CHOYSEN if you build my repo you didn't get that ?

Yes, i clone your repo and build it, then start a server with koa, it work fine for me

[stephanedemotte]

@CHOYSEN It's crazy you don't have

{ "_rawValue": false, "_shallow": false, "__v_isRef": true, "_value": false }

After the build ?

I cannot believe it :/ Can you share a screen please ?

I've tried again from scratch, and i've got the same result
App [{{ isActive }}] should return App[true] but got App [{ "_rawValue": false, "_shallow": false, "__v_isRef": true, "_value": false }]

[CHOYSEN]

@stephanedemotte

I find it, you should remove your yarn.lock and node_modules, then run yarn again

[CHOYSEN]

@stephanedemotte

There are some vue3.0.3 information in the file, which should be caused by this

[stephanedemotte]

@CHOYSEN thanks a lot, and very sorry for the noise :)