[BUG] Command was killed with SIGSEGV (Segmentation fault): plasmo de

[gitNetw0rk]

What happened?

Recently I upgraded to plasmo. I am not sure if that is the reason, but I cannot build the project anymore.

Anybody else experience this?
🔄 Building. ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command was killed with SIGSEGV (Segmentation fault): plasmo dev

Version

Latest

What OS are you seeing the problem on?

Linux

What browsers are you seeing the problem on?

Firefox

Relevant log output

🟣 Plasmo v0.90.3
🔴 The Browser Extension Framework
🔵 INFO   | Starting the extension development server...
🔵 INFO   | Building for target: chrome-mv3
🔵 INFO   | Loaded environment variables from: [ '.env.chrome' ]
🔄 Building.. ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command was killed with SIGSEGV (Segmentation fault): plasmo dev

(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.

[therealhnk]

Same problem here

🟣 Plasmo v0.90.3
🔴 The Browser Extension Framework
🔵 INFO | Prepare to bundle the extension...
🔵 INFO | Building for target: chrome-mv3
🔵 INFO | Loaded environment variables from: []
DEPRECATION WARNING [legacy-js-api]: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

More info: https://sass-lang.com/d/legacy-js-api

DEPRECATION WARNING [legacy-js-api]: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

More info: https://sass-lang.com/d/legacy-js-api

DEPRECATION WARNING [legacy-js-api]: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.

More info: https://sass-lang.com/d/legacy-js-api

Segmentation fault (core dumped)
 ELIFECYCLE  Command failed with exit code 139.
Error: Process completed with exit code 139.

[gitNetw0rk]

Here is workaround @therealhnk. I realized this issue was caused by the 'parcel' package, which could not upgrade. I fixed it by pinning parcel to version 2.8.3 (see: #661 (comment)). Then I install the project with --with-nextjs, which does not install parcel at all. The issue is gone. Consider moving the project onto nextjs basis (the build is pretty much the same size).

[pippinmole]

Duplicate #1156