Regression in plugin-vue 1.8 can't import const enum

[jods4]

Describe the bug

My project uses Typescript const enum.
During dev, it goes through esbuild and they are handled like regular enums, no problem.
When building for prod, I have tweaked my vite config to use tsc compiler, so const enums actually work as they should (they're replaced by constants).

This was all fine until plugin-vue version 1.7.0.
After upgrading to 1.8.0 my build fails with an error that says "ImportedEnum is not exported by ModuleThatExportsEnum".

Reproduction

vite.config.js that uses TS to build for prod:

import { defineConfig } from "vite";
import vue from "@vitejs/plugin-vue";
import ts from "rollup-plugin-typescript2";

export default defineConfig(({ command, mode }) => ({
  plugins: [ vue() ],
  esbuild: command !== "build",
  {
    apply: "build",
    ...ts({ abortOnError: false, check: false }),
  },
}))

All you need now is an exported const enum, e.g. enums.ts:

export const enum E { a = 1, b = 2 }

And a vue file that consumes it, e.g. test.vue:

<template>Hello</template>

<script setup type="ts">
  import { E } from "./enums"

  if (E.a > 0) console.log(":wave:")
</script>

If you run vite build with plugin-vue >= 1.8.0 it will fail.

System Info

System:
    OS: Windows 10 10.0.18363
    CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
    Memory: 4.24 GB / 15.79 GB
  Binaries:
    Node: 16.6.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.19.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.18362.1593.0)
    Internet Explorer: 11.0.18362.1766

Used Package Manager

npm

Logs

Error: 'AuditChange' is not exported by Services\user.ts, imported by Modules\Users\Components\user.vue

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.

[sapphi-red]

This is caused by this change.
93d9a2d#diff-50999b66ad3fff48fd315417d4f8c98741da9f85a0fa6bb4ba212cc8f8bac967L271-R267
The same reason with #5044.

[jods4]

@sapphi-red thanks for debugging this! Hopefully that can lead to a fix.
I can confirm this is still an issue in plugin-vue 2.3.1 -- it's an upgrade blocker.

[jods4]

I tested with my project and can confirm @sapphi-red is right, this is the culprit here.
I see what's happening and I'll create a new issue that has a better description of the general problem, rather than its symptoms.

[patak-dev]

Fixed by #7909