About @vitejs/plugin-legacy does not support library mode #1639

gjactat · 2021-01-22T11:26:18Z

Is your feature request related to a problem? Please describe.
I'm a long time user of Vue in a webpack context and i'm giving a try to Vite.
So far It's been a pleasant journey : Dev mode is really impressive !

My project consists of several standalone Vue components that are instantiated on demand from Vanilla Javascript.
This is why they are currently built with the Webpack Library mode which works just fine.

I have successfully built these components with Vite (with dynamic import and everything) and they work juts fine on modern browser.

Describe the solution you'd like
I'd like to also build those components for legacy browsers... And this is currently not allowed (error message : "@vitejs/plugin-legacy does not support library mode").

I'd like to know if there is still hope for this specific use case ?... And I also like to mention that these legacy builds don't have to be as polished as the es ones (considering that they will only be served to a small percentage of our visitors).

While I wish to give the best experience to the vast majority of my users (equipped with modern browsers), I would be fine with monolithic builds, without any code splitting or dynamic imports for legacy browsers. Maybe with something like Rollup's "inlineDynamicImports" ? After all, these legacy builds should vanish eventually.

Describe alternatives you've considered

Additional context
Add any other context or screenshots about the feature request here.

Jeaciaz · 2021-04-13T14:26:54Z

Would love to see this implemented. As a developer who has to support IE11, Vite and its out-of-the-box speed and ease of use has been a blessing until I learned library mode doesn't support IE11 :(

stefandesu · 2021-04-15T08:07:43Z

I've been trying to get my library that was built with Vite working with https://observablehq.com, but so far to no avail. I thought maybe a legacy build would help, but unfortunately, that doesn't work at the moment as discussed here. 🤔

lovasoa · 2021-08-07T17:21:23Z

Hello !
@yyx990803 : what do you think would be needed to get that to work ? I have users on sanipasse.fr who are on old browsers and for whom the site is currently broken. I would be happy to contribute, but have no idea where to start.

tylerrrkd · 2021-11-09T03:25:54Z

Would love to see this implemented. As a developer who has to support IE11, Vite and its out-of-the-box speed and ease of use has been a blessing until I learned library mode doesn't support IE11 :(

Hope support soon.

skyweaver213 · 2021-12-10T02:34:38Z

Hope support soon.

lovasoa · 2022-01-25T15:56:10Z

Happy birthday to this issue 🎈🥳

fychinesepjj · 2022-02-08T08:26:34Z

Hope support soon.

wenjoy · 2022-02-15T08:27:07Z

IMHO, app which import the lib should care about to bunde it to be capable of old browser. It's not like build a site. So @vitejs/plugin-legacy doesn't need to support some IE 11. Thoughts?

wenjoy · 2022-02-15T09:28:02Z

I have figured out a solution to bundle lib supporting old browser without dependent @vitejs/plugin-legacy although I insist that lib no need to worry about it.

Here is a sample config, hope to help anyone encountered this:

//vite.config.js
import { babel } from '@rollup/plugin-babel';
...
 plugins: [
    babel({
      babelHelpers: 'runtime',
      extensions: ['.js', '.jsx', '.es6', '.es', '.mjs', 'ts'],
    })
]

//babel.config.js

module.exports = {
  presets: [
    [
      '@babel/env',
      {
        useBuiltIns: 'usage',
        corejs: 3,
      },
    ],
  ],
  plugins: ['@babel/plugin-transform-runtime'],
};

//package.json
  "browserslist": [
    "> 0.5%",
    "not dead"
  ],

agileago · 2022-02-15T09:30:16Z

@wenjoy ts is ok ? i think esbuild will deal the ts file but babel will not

wenjoy · 2022-02-15T09:50:30Z

@wenjoy ts is ok ? i think esbuild will deal the ts file but babel will not

esbuild will not transform to es5, but we cant config to let babel can handle ts even transform to es5.

agileago · 2022-02-15T11:15:21Z

我知道，你测试过这样写会进行转换ts么

gyurielf · 2022-04-06T15:54:12Z

@wenjoy ts is ok ? i think esbuild will deal the ts file but babel will not

esbuild will not transform to es5, but we cant config to let babel can handle ts even transform to es5.

But the question is how ? :D

xjccc · 2022-06-06T10:15:37Z

@wenjoy ts is ok ? i think esbuild will deal the ts file but babel will not

esbuild will not transform to es5, but we cant config to let babel can handle ts even transform to es5.

But the question is how ? :D
i tried, but the error told me Rollup failed to resolve import "@babel/runtime/helpers/typeof"

eleven-net-cn · 2022-09-22T08:04:50Z

The following method should solve the problem, e.g:

// vite.config.js (e.g)
const { getBabelOutputPlugin } = require('@rollup/plugin-babel');

export default {
  build: {
    rollupOptions: {
      plugins: [
        /**
         * Running Babel on the generated code:
         *  https://github.com/rollup/plugins/blob/master/packages/babel/README.md#running-babel-on-the-generated-code
         *
         * Transforming ES6+ syntax to ES5 is not supported yet, there are two ways to do:
         *  https://github.com/evanw/esbuild/issues/1010#issuecomment-803865232
         * We choose to run Babel on the output files after esbuild.
         *
         * @vitejs/plugin-legacy does not support library mode:
         *  https://github.com/vitejs/vite/issues/1639
         */
        getBabelOutputPlugin({
          allowAllFormats: true,
          presets: [
            [
              '@babel/preset-env',
              {
                useBuiltIns: false, // Default：false
                // Exclude transforms that make all code slower
                exclude: ['transform-typeof-symbol'],
                // https://babeljs.io/docs/en/babel-preset-env#modules
                modules: false,
              },
            ],
          ],
          plugins: [
            /**
             * Extract the helper function.
             */
            [
              '@babel/plugin-transform-runtime',
              {
                corejs: false,
                // version: require('@babel/runtime').version,
              },
            ],
          ],
        }),
      ],
    },
  },
};

Running babel on the generated code by esbuild (vite).

The presets and plugins configuration of babel is only suitable for me, you can modify it.

jiakangning · 2022-10-11T01:57:46Z

I have figured out a solution to bundle lib supporting old browser without dependent @vitejs/plugin-legacy although I insist that lib no need to worry about it.

Here is a sample config, hope to help anyone encountered this:

//vite.config.js
import { babel } from '@rollup/plugin-babel';
...
 plugins: [
    babel({
      babelHelpers: 'runtime',
      extensions: ['.js', '.jsx', '.es6', '.es', '.mjs', 'ts'],
    })
]

//babel.config.js

module.exports = {
  presets: [
    [
      '@babel/env',
      {
        useBuiltIns: 'usage',
        corejs: 3,
      },
    ],
  ],
  plugins: ['@babel/plugin-transform-runtime'],
};

//package.json
  "browserslist": [
    "> 0.5%",
    "not dead"
  ],

its useful for js application when use vite

dparker2 · 2022-11-17T19:41:47Z

IMHO, app which import the lib should care about to bunde it to be capable of old browser. It's not like build a site. So @vitejs/plugin-legacy doesn't need to support some IE 11. Thoughts?

This rationale does not consider building a UMD formatted bundle (which is one of the default build formats), or an IIFE format, both of which can be directly included onto a page in older browsers.

woai3c · 2023-06-25T08:36:47Z

it's work for me:

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

gaomAndximi · 2023-10-25T08:35:52Z

it's work for me:

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

it works！

GrinZero · 2023-11-09T10:38:39Z

When I use useBuiltIns:"useage"，It can't run......

GrinZero · 2023-11-09T10:39:53Z

In fact, it look like import"core-js/modules/esnext.global-this.js"; in my bundle file.But I want to use "inline" mode.

Lpmvb · 2023-12-08T06:57:37Z

it's work for me:

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

replaceAll not be polyfill

yin-shu · 2024-01-19T08:20:34Z

it's work for me:这对我有用：

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

我这样配置后，构建产物里有旧浏览器不支持的语法：

 var createPropertyDescriptor$8 = function createPropertyDescriptor2(bitmap, value) {
    return {
      enumerable: !(bitmap & 1),
      configurable: !(bitmap & 2),
      writable: !(bitmap & 4),
      value
    };
  };

这里的 'value' 在旧浏览器中不兼容，这些代码应该是babel 加入进去的，很奇怪，我使用版本是：

"@babel/plugin-transform-runtime": "^7.23.7",
    "@babel/preset-env": "^7.23.8",
    "@babel/runtime": "^7.23.8",
    "@babel/runtime-corejs3": "^7.23.8",
    "@rollup/plugin-babel": "^5.3.1",
    "vite": "^5.0.11",

yoyo837 · 2024-01-19T10:12:26Z

it's work for me:这对我有用：

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

我这样配置后，构建产物里有旧浏览器不支持的语法：

 var createPropertyDescriptor$8 = function createPropertyDescriptor2(bitmap, value) {
    return {
      enumerable: !(bitmap & 1),
      configurable: !(bitmap & 2),
      writable: !(bitmap & 4),
      value
    };
  };

这里的 'value' 在旧浏览器中不兼容，这些代码应该是babel 加入进去的，很奇怪，我使用版本是：

"@babel/plugin-transform-runtime": "^7.23.7",
    "@babel/preset-env": "^7.23.8",
    "@babel/runtime": "^7.23.8",
    "@babel/runtime-corejs3": "^7.23.8",
    "@rollup/plugin-babel": "^5.3.1",
    "vite": "^5.0.11",

你这个配置 polyfill 是运行时的，如果想要 umd 自带 polyfill, babelHelpers 应该为 bundled，并且去掉 @babel/plugin-transform-runtime

yin-shu · 2024-01-19T10:45:03Z

it's work for me:这对我有用：

pnpm i -D @babel/plugin-transform-runtime @babel/preset-env @babel/runtime @rollup/plugin-babel

// vite.config.ts
import { fileURLToPath, URL } from 'node:url'
import { resolve } from 'path'
import type { ConfigEnv, UserConfigExport } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import svgLoader from 'vite-svg-loader'
import cssInjectedByJsPlugin from 'vite-plugin-css-injected-by-js'
import babel from '@rollup/plugin-babel'

export default ({ command, mode }: ConfigEnv): UserConfigExport => {
    const config: UserConfigExport = {
        plugins: [vue(), vueJsx(), cssInjectedByJsPlugin(), svgLoader()],
        resolve: {
            alias: {
                '@': fileURLToPath(new URL('./src', import.meta.url)),
            },
        },
        build: {
            minify: 'terser',
            terserOptions: {
                compress: {
                    drop_console: true,
                    drop_debugger: true,
                },
            },
            lib: {
                entry: resolve(__dirname, 'src/index.ts'),
                name: 'IntegrationPlatformNavbar',
                fileName: 'integration-platform-navbar',
            },
            rollupOptions: {
                // 确保外部化处理那些你不想打包进库的依赖
                external: ['vue', 'element-plus'],
                output: {
                    // 在 UMD 构建模式下为这些外部化的依赖提供一个全局变量
                    globals: {
                        vue: 'Vue',
                        'element-plus': 'ElementPlus',
                    },
                },
                plugins: [
                    babel({
                        extensions: ['.js', '.ts', '.vue'],
                        babelHelpers: 'runtime',
                        plugins: ['@babel/plugin-transform-runtime'],
                        presets: [
                            [
                                '@babel/preset-env',
                                {
                                    useBuiltIns: false,
                                    targets: {
                                        browsers: ['last 2 versions', '> 1%', 'not ie <= 11'],
                                    },
                                },
                            ],
                        ],
                    }),
                ],
            },
        },
    }

    return config
}

我这样配置后，构建产物里有旧浏览器不支持的语法：

 var createPropertyDescriptor$8 = function createPropertyDescriptor2(bitmap, value) {
    return {
      enumerable: !(bitmap & 1),
      configurable: !(bitmap & 2),
      writable: !(bitmap & 4),
      value
    };
  };

这里的 'value' 在旧浏览器中不兼容，这些代码应该是babel 加入进去的，很奇怪，我使用版本是：

"@babel/plugin-transform-runtime": "^7.23.7",
    "@babel/preset-env": "^7.23.8",
    "@babel/runtime": "^7.23.8",
    "@babel/runtime-corejs3": "^7.23.8",
    "@rollup/plugin-babel": "^5.3.1",
    "vite": "^5.0.11",

你这个配置 polyfill 是运行时的，如果想要 umd 自带 polyfill, babelHelpers 应该为 bundled，并且去掉 @babel/plugin-transform-runtime

我这样改了，构建产物里还是有 { value, } 的代码，这里有个在线实例可验证，希望能帮我看下怎么调整：
https://stackblitz.com/edit/vitejs-vite-fip7pv?file=vite.config.ts

在 dist/vite-ts.umd.js 里 410 行可以看到

yoyo837 · 2024-01-19T11:08:27Z

@yin-shu 我这编译没有这个问题，但是我这是直接rollup的。你提供的链接我空了再看看。

yin-shu · 2024-01-20T09:37:23Z

我测试直接用rollup没问题，但在vite中使用不行

thjjames · 2024-02-28T09:28:22Z

The following method should solve the problem, e.g:

// vite.config.js (e.g)
const { getBabelOutputPlugin } = require('@rollup/plugin-babel');

export default {
  build: {
    rollupOptions: {
      plugins: [
        /**
         * Running Babel on the generated code:
         *  https://github.com/rollup/plugins/blob/master/packages/babel/README.md#running-babel-on-the-generated-code
         *
         * Transforming ES6+ syntax to ES5 is not supported yet, there are two ways to do:
         *  https://github.com/evanw/esbuild/issues/1010#issuecomment-803865232
         * We choose to run Babel on the output files after esbuild.
         *
         * @vitejs/plugin-legacy does not support library mode:
         *  https://github.com/vitejs/vite/issues/1639
         */
        getBabelOutputPlugin({
          allowAllFormats: true,
          presets: [
            [
              '@babel/preset-env',
              {
                useBuiltIns: false, // Default：false
                // Exclude transforms that make all code slower
                exclude: ['transform-typeof-symbol'],
                // https://babeljs.io/docs/en/babel-preset-env#modules
                modules: false,
              },
            ],
          ],
          plugins: [
            /**
             * Extract the helper function.
             */
            [
              '@babel/plugin-transform-runtime',
              {
                corejs: false,
                // version: require('@babel/runtime').version,
              },
            ],
          ],
        }),
      ],
    },
  },
};

Running babel on the generated code by esbuild (vite).

The presets and plugins configuration of babel is only suitable for me, you can modify it.

in lib mode, code is generated by rollup & rollup-plugin-typescript other than esbuild when 'vite build' exec

djkloop · 2024-06-05T03:55:46Z

我测试直接用rollup没问题，但在vite中使用不行

// 直接这样试一试，把那些多余的rollup插件去掉
{
	build: {
		target: ["es2015"]
	}
}

mikaelkarlsson-se · 2024-10-09T11:25:49Z

When I use useBuiltIns:"useage"，It can't run......

You will likely need to install core-js separately, see https://babeljs.io/docs/babel-preset-env#usebuiltins

yyx990803 added the enhancement New feature or request label Jan 22, 2021

lovasoa mentioned this issue Jun 30, 2021

support legacy browsers lovasoa/sanipasse#18

Open

lovasoa mentioned this issue Aug 5, 2021

Fonctionnement avec les anciens navigateurs lovasoa/sanipasse#43

Open

Niputi added feat: library mode plugin: legacy labels Jan 26, 2022

vilbergs mentioned this issue Aug 3, 2022

Compatibility with @vite/plugin-legacy laravel/vite-plugin#114

Closed

sapphi-red mentioned this issue Aug 28, 2022

cannot support @rollup/plugin-babel #9751

Closed

7 tasks

fritx mentioned this issue Sep 4, 2022

Do you have any plans to support vue3? fritx/vue-at#137

Open

patak-dev added this to Team Board Mar 10, 2023

github-project-automation bot moved this to Discussing in Team Board Mar 10, 2023

patak-dev removed this from Team Board Mar 10, 2023

sadn1ck mentioned this issue Oct 17, 2023

Error: @vitejs/plugin-legacy does not support library mode. #14671

Closed

7 tasks

alexookah mentioned this issue Dec 8, 2023

Plugin legacy is not working as expected for replaceAll #15293

Closed

7 tasks

Olivki mentioned this issue Mar 4, 2024

vite.config.ts doesn't work MDReal32/bundled-kubejs#6

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

About @vitejs/plugin-legacy does not support library mode #1639

About @vitejs/plugin-legacy does not support library mode #1639

gjactat commented Jan 22, 2021 •

edited

Loading

Jeaciaz commented Apr 13, 2021

stefandesu commented Apr 15, 2021

lovasoa commented Aug 7, 2021 •

edited

Loading

tylerrrkd commented Nov 9, 2021

skyweaver213 commented Dec 10, 2021

lovasoa commented Jan 25, 2022

fychinesepjj commented Feb 8, 2022

wenjoy commented Feb 15, 2022

wenjoy commented Feb 15, 2022

agileago commented Feb 15, 2022

wenjoy commented Feb 15, 2022

agileago commented Feb 15, 2022

gyurielf commented Apr 6, 2022

xjccc commented Jun 6, 2022

eleven-net-cn commented Sep 22, 2022 •

edited

Loading

jiakangning commented Oct 11, 2022 •

edited

Loading

dparker2 commented Nov 17, 2022 •

edited

Loading

woai3c commented Jun 25, 2023

gaomAndximi commented Oct 25, 2023

GrinZero commented Nov 9, 2023

GrinZero commented Nov 9, 2023

Lpmvb commented Dec 8, 2023

yin-shu commented Jan 19, 2024

yoyo837 commented Jan 19, 2024

yin-shu commented Jan 19, 2024

yoyo837 commented Jan 19, 2024

yin-shu commented Jan 20, 2024

thjjames commented Feb 28, 2024

djkloop commented Jun 5, 2024 •

edited

Loading

mikaelkarlsson-se commented Oct 9, 2024

About @vitejs/plugin-legacy does not support library mode #1639

About @vitejs/plugin-legacy does not support library mode #1639

Comments

gjactat commented Jan 22, 2021 • edited Loading

Jeaciaz commented Apr 13, 2021

stefandesu commented Apr 15, 2021

lovasoa commented Aug 7, 2021 • edited Loading

tylerrrkd commented Nov 9, 2021

skyweaver213 commented Dec 10, 2021

lovasoa commented Jan 25, 2022

fychinesepjj commented Feb 8, 2022

wenjoy commented Feb 15, 2022

wenjoy commented Feb 15, 2022

agileago commented Feb 15, 2022

wenjoy commented Feb 15, 2022

agileago commented Feb 15, 2022

gyurielf commented Apr 6, 2022

xjccc commented Jun 6, 2022

eleven-net-cn commented Sep 22, 2022 • edited Loading

jiakangning commented Oct 11, 2022 • edited Loading

dparker2 commented Nov 17, 2022 • edited Loading

woai3c commented Jun 25, 2023

gaomAndximi commented Oct 25, 2023

GrinZero commented Nov 9, 2023

GrinZero commented Nov 9, 2023

Lpmvb commented Dec 8, 2023

yin-shu commented Jan 19, 2024

yoyo837 commented Jan 19, 2024

yin-shu commented Jan 19, 2024

yoyo837 commented Jan 19, 2024

yin-shu commented Jan 20, 2024

thjjames commented Feb 28, 2024

djkloop commented Jun 5, 2024 • edited Loading

mikaelkarlsson-se commented Oct 9, 2024

gjactat commented Jan 22, 2021 •

edited

Loading

lovasoa commented Aug 7, 2021 •

edited

Loading

eleven-net-cn commented Sep 22, 2022 •

edited

Loading

jiakangning commented Oct 11, 2022 •

edited

Loading

dparker2 commented Nov 17, 2022 •

edited

Loading

djkloop commented Jun 5, 2024 •

edited

Loading