Dmitriy Fuks
With this, there is another issue: I use the plugin @rollup/plugin-babel for transpiling to legacy browsers using the getBabelOutputPlugin mode. The code that Vite adds (__vite__mapDeps) is the only thing...
I encountered a [similar problem](https://github.com/swc-project/plugins/issues/261) related to upgrading `@swc/core` to version 1.3.106. I am developing an external library and cannot force all consumers to specify resolutions in package.json :( It...
@ArnaudBarre I'm developing a library-bundler based on Vite, which is used for building frontends within our company. It has the following dependencies: ```json "@swc/plugin-styled-components": "1.5.116", "@vitejs/plugin-react-swc": "3.5.0", ``` We use...
I don't see anything wrong with loading 2 versions of `@swc/core` - one just won't be used. Library users install it with a simple command `yarn add @my-org/frontend-scripts`. In this...
Perhaps you misunderstood me. We don't use Vite for library builds. It's used as part of our internal library for building Vite-based applications. But alright. I got you - I'll...
Why was it closed? :( I have the same problem with arrow function components
@cjsauer I have the same problem
@acuthbert There is another issue with this solution. https://github.com/typeorm/typeorm/pull/9354#issuecomment-1579362570