vite-plugin-react-swc: Segmentation fault in a fresh React project if using plugins
When I try to create a new Vite project using yarn create vite
and selecting React with Typescript + SWC, I can perform yarn build
just fine, however when I yarn add -D @swc/plugin-emotion
and update my Vite config, the build fails with a segmentation fault.
I also get the same result with @swc/plugin-noop
and @swc/plugin-styled-components
.
vite.config.ts
:
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react-swc'
// https://vitejs.dev/config/
export default defineConfig({
plugins: [react({
plugins: [['@swc/plugin-emotion', {}]]
})],
})
package.json
{
"name": "testing1234",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0",
"preview": "vite preview"
},
"dependencies": {
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@swc/plugin-emotion": "^2.5.115",
"@types/react": "^18.2.43",
"@types/react-dom": "^18.2.17",
"@typescript-eslint/eslint-plugin": "^6.14.0",
"@typescript-eslint/parser": "^6.14.0",
"@vitejs/plugin-react-swc": "^3.5.0",
"eslint": "^8.55.0",
"eslint-plugin-react-hooks": "^4.6.0",
"eslint-plugin-react-refresh": "^0.4.5",
"typescript": "^5.2.2",
"vite": "^5.0.8"
}
}
Running yarn build
gets stuck at this step:
-> % yarn build
yarn run v1.22.21
$ tsc && vite build
vite v5.0.12 building for production...
transforming (1) index.html
After some time, it crashes with SIGSEGV
-> % yarn build
yarn run v1.22.21
$ tsc && vite build
vite v5.0.12 building for production...
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I’m running Arch Linux, node v20.9.0.
About this issue
- Original URL
- State: open
- Created 5 months ago
- Reactions: 1
- Comments: 15 (5 by maintainers)
I have experienced the same issue with the
@swc/plugin-styled-components
. Going down to the@swc/plugin-styled-components@1.5.111
fixed it for me.