multiple vite bundle import in one page throw:Uncaught SyntaxError: Identifier 'React' has already been declared

[joebnb]

Describe the bug

when multiple vite bundle import in one page will throw " Identifier 'Fa' has already been declared " in console.

bundle 1 fold level 1 screenshot:

the bundle 2 fold level 1 screenshot:

i have already to try：

• set minify with false in one of bunde
• switch minify to terser and disable mangle and compress

it's still output some mangled variable was decleared.

when set both bundle with minify false it output:

my vite config is

import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

// https://vitejs.dev/config/
export default defineConfig({
    plugins: [react()],
    build: {
        outDir: '../../lib/client',
        manifest: true,
        target: 'es2020',
        rollupOptions: {
            output: {
                chunkFileNames: 'assets/[name].js',
                entryFileNames: 'assets/[name].js',
                assetFileNames: 'assets/[name].[ext]',
                manualChunks: {},
            },
        },
        minify: false,
    },
    server: {
        host: '0.0.0.0',
        port: 3000,
        cors: {
            origin: '*',
        },
    },
});

how could i to fix it, PuruVJ/vite-preset-react#5 i found this issue during write this,not sure did this is helpful to solve this.

Reproduction

no

Steps to reproduce

No response

System Info

System:
    OS: macOS 13.0
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 108.93 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.0 - /usr/local/bin/node
    npm: 8.19.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 107.0.5304.87
    Safari: 16.1

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 vuejs/core 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.

[joebnb]

if one is import with vite dev model it's works well

[joebnb]

if wrap with a IIFE it's works as expect

i think it's a bug of vite,it should be fix

[github-actions]

Hello @joebnb. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[luwes]

this seems still to be a bug, at least with Nuxt 3.

Vite injected this import at the top of our minified bundles with no regard for variable collision

import { h } from '/_nuxt/node_modules/.vite/deps/vue.js?v=8f0c34a1';

[joebnb]

vuejs/core#7206 vue3 also have this problem