[BUG] Segmentation fault during build

[mreinertssgr]

What happened?

Plasmo segfaults when I try to build my extension, these are the relevant parts of my package.json

    "scripts": {
        "dev": "bun run watch-routes & plasmo dev",
        "generate-routes": "tsr generate",
        "watch-routes": "tsr watch",
        "build": "bun run generate-routes && plasmo build",
        "package": "bun run generate-routes && plasmo package"
    },
    "dependencies": {
        "@emotion/react": "^11.13.3",
        "@emotion/styled": "^11.13.0",
        "@fortawesome/fontawesome-pro": "^6.6.0",
        "@fortawesome/fontawesome-svg-core": "^6.6.0",
        "@fortawesome/free-brands-svg-icons": "^6.6.0",
        "@fortawesome/free-solid-svg-icons": "^6.6.0",
        "@fortawesome/pro-light-svg-icons": "^6.6.0",
        "@fortawesome/react-fontawesome": "^0.2.2",
        "@mui/icons-material": "^6.0.0",
        "@mui/material": "^5.16.7",
        "@plasmohq/messaging": "^0.6.2",
        "@plasmohq/storage": "^1.11.0",
        "@tanstack/react-form": "^0.26.4",
        "@tanstack/react-query": "^5.52.2",
        "@tanstack/react-router": "^1.51.0",
        "@tanstack/router-devtools": "^1.51.0",
        "@tanstack/router-plugin": "^1.51.0",
        "@tanstack/router-zod-adapter": "^1.53.1",
        "@tanstack/zod-form-adapter": "^0.32.0",
        "@types/bcryptjs": "^2.4.6",
        "@uidotdev/usehooks": "^2.4.1",
        "bcryptjs": "^2.4.3",
        "crypto-js": "^4.2.0",
        "framer-motion": "^11.3.30",
        "i18next": "^23.14.0",
        "i18next-browser-languagedetector": "^8.0.0",
        "i18next-http-backend": "^2.6.1",
        "otpauth": "^9.3.2",
        "plasmo": "0.89.1",
        "react": "18.2.0",
        "react-countdown-circle-timer": "^3.2.1",
        "react-dom": "18.2.0",
        "react-hot-toast": "^2.4.1",
        "react-i18next": "^15.0.1",
        "zod": "^3.23.8",
        "zustand": "^4.5.5"
    },
    "devDependencies": {
        "@biomejs/biome": "1.8.3",
        "@types/crypto-js": "^4.2.2",
        "@ianvs/prettier-plugin-sort-imports": "4.1.1",
        "@tanstack/router-cli": "^1.51.0",
        "@types/chrome": "0.0.258",
        "@types/node": "20.11.5",
        "@types/react": "18.2.48",
        "@types/react-dom": "18.2.18",
        "autoprefixer": "^10.4.20",
        "postcss": "^8.4.41",
        "prettier": "3.2.4",
        "tailwindcss": "^3.4.10",
        "typescript": "5.3.3"
    },
    "peerDependencies": {
        "react": "^18.0.0",
        "react-dom": "^18.0.0"
    },

Version

Latest

What OS are you seeing the problem on?

MacOSX

What browsers are you seeing the problem on?

Chrome

Relevant log output

🟡 20     | Creating BGSW entry
🟡 21     | Hash changed, updating manifest
🔵 INFO   | Loaded environment variables from: [ '.env' ]
🟡 0      | @plasmohq/parcel-transformer-manifest
🟠 WARN   | default_locale not set, fallback to en
🟡 1      | Adding locale en
🟡 2      | Adding icons
🟡 3      | Adding default_icon
🟡 4      | Adding default_popup
🟡 5      | Adding page
🟡 6      | Handling MV3 background service worker
🟡 7      | + Finished transforming manifest
🟡 0      | @plasmohq/parcel-bundler
/bin/bash: line 1: 88367 Segmentation fault: 11  plasmo build --verbose
error: script "build" exited with code 139

(OPTIONAL) Contribution

• I would like to fix this BUG via a PR

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.

[hmps]

👋 @mreinertssgr

I had this too. Upgrading to Node 22.10 fixed it for me. See parcel-bundler/parcel#9926 for more info.

[DenizUgur]

I'm with Node v22.13 and I encounter a similar issue. Let me know what kind of information you'd need to investigate this. I'm on Ubuntu 24.10 (amd64) and using plasmo 0.89.4.

[pippinmole]

Duplicate of #1156