[BUG] TailwindCSS example does not build #1156

DenizUgur · 2025-01-13T02:16:40Z

What happened?

I'm getting segmentation fault for building the TailwindCSS example. I haven't changed anything inside the example and just built the example as-is.

pnpm create plasmo --with-tailwindcss
pnpm build

Removing references to the stylesheet with tailwind directives does not result in the segmentation fault but of course this is not a fix.

Related to #1089 I suppose.

Versions:
Node: v22.13.0
pnpm: 9.15.3
plasmo: v0.89.4

Version

Latest

What OS are you seeing the problem on?

Linux

What browsers are you seeing the problem on?

No response

Relevant log output

🟣 Plasmo v0.89.4
🔴 The Browser Extension Framework
🔵 INFO   | Prepare to bundle the extension...
🔵 INFO   | Building for target: chrome-mv3
🔵 INFO   | Loaded environment variables from: []
(node:88306) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Segmentation fault (core dumped)
 ELIFECYCLE  Command failed with exit 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.

gregoryPacific · 2025-01-14T17:17:59Z

I'm facing the same issue in a project.

It's important to note that the pnpm plasmo dev command works, but the pnpm plasmo build command does not.

Even though an error appears, it seems that Plasmo is still able to generate the build somehow, as the build files are being generated.

Versions:
Node: v18.18.0
pnpm: v9.15.4
plasmo: v0.89.4

Version

Latest

What OS are you seeing the problem on?

Ubuntu 24.04.1 LTS running on WSL2

Relevant log output:

spiceworm · 2025-01-15T02:41:58Z

I am also experiencing this issue.

detronetdip · 2025-01-23T07:51:29Z

Any update on this? I'm also facing he same issue

gregoryPacific · 2025-01-23T12:06:08Z

I think there are conflicts between subdependencies and Plasmo after running the pnpm update on an older project. These conflicts caused problems on build and I had to roll back the changes on pnpm-lock.yaml to restore functionality.

I suspect that a sub-dependency in its newest version is causing this issue, but I haven't been able to pinpoint it.

ahmedazizkhelifi · 2025-02-03T10:55:31Z

I faced the same issue; pnpm run dev works, but the build script does not.

I resolved this by downgrading pnpm to version 7.33.7 btw, I’m using Plasmo 0.57.2

osarhan · 2025-02-03T16:52:41Z

@ahmedazizkhelifi I just did that, and it worked for me as well! Thanks for the tip. Now I am trying to figure out what im missing from plasmo between 0.57.2 to 0.89.4.

btw, I was able to still use the latest version of pnpm

Edit:
The latest version I can get mine to build with is plasmo version 0.78.0, but nothing later than that. One thing to note is that I use the sidepanel for my extension, and version 0.79.0 introduces that. so having the side panel api, and that version seems to break the build process.

osarhan · 2025-02-06T00:24:02Z

FYI - For what its worth, build works on my mac M2. However does not build in docker.

pippinmole · 2025-02-07T17:40:45Z

Getting this error when running plasmo build --target=chrome-mv3 in a GitHub CI.

Is this project still maintained? Last commit to main 3 months ago, and I'm not seeing many responses from maintainers.

osarhan · 2025-02-07T18:00:57Z

It's frustrating. However, this framework has been a godsend. So I'm thankful it exists. Has helped me develop my extension tremendously.

I have to deploy everything locally to avoid this build error. Im thinking this build error was an oversight due to it working locally, and not in a CI/CD environment.

Btw. Are you developing an extension with the side panel? I am, so I keep thinking that's the culprit.

pippinmole · 2025-02-07T18:06:32Z

However, this framework has been a godsend.

I agree. But dropping off the face of the earth for 3 months is a sign to steer clear. And I don't want to steer clear

Btw. Are you developing an extension with the side panel? I am, so I keep thinking that's the culprit.

I'm not using the feature, but the build cache does have a sidepanel.tsx with some code in it. I'm happy to provide more info if you ask specific questions - I don't fully understand how sidepanels work :)

osarhan · 2025-02-07T18:09:27Z

Hmm. Interesting.

If you're not using the sidepanel, I would downgrade your plasmo version to 0.78.0 and see if it builds in your ci/cd. 0.79.0 introduced the side panels api, and doesn't build for me.

For me I'm kind of screwed since I built my entire extension using side panel. 🫠

ahmedazizkhelifi · 2025-02-07T18:17:09Z

If you're not using the sidepanel, I would downgrade your plasmo version to 0.78.0 and see if it builds in your ci/cd. 0.79.0 introduced the side panels api, and doesn't build for me.

I'm using GitHub CI/CD to build the extension, and it works without issues. If you don’t need the features introduced in ^0.79.0, downgrading to 0.78.0 should resolve the build problem.

pippinmole · 2025-02-07T18:20:14Z

@ahmedazizkhelifi

I'm using GitHub CI/CD to build the extension

Is this on version 0.78.0? Or latest?

osarhan · 2025-02-07T18:20:30Z

I have never contributed to this code base. But if I have time this weekend I may poke around to see if the side panel isn't being used, to not cache it to avoid the build failure...

ahmedazizkhelifi · 2025-02-07T18:25:24Z

I faced the same issue; pnpm run dev works, but the build script does not.

I resolved this by downgrading pnpm to version 7.33.7 btw, I’m using Plasmo 0.57.2

@pippinmole Well, im using plasmo 0.57.2 and pnpm 7

    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Install Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 16

      - uses: pnpm/[email protected]
        name: Install pnpm
        id: pnpm-install
        with:
          version: 7
          run_install: false

@osarhan Have you tried downgrading the pnpm version instead of Plasmo?

osarhan · 2025-02-07T18:37:56Z

Yeah downgrading on pnpm doesn't solve it for me. 😵‍💫 And I need the ^0.79.0 version since I'm dependent on side panel.

Latest version of pnpm and 0.78 version of plasmo builds fine.

pippinmole · 2025-02-07T19:30:30Z

Might not be the place to post, but downgrading to 0.78.0 gives me this error when trying to build.

pippinmole · 2025-02-07T20:35:18Z

Short term fix for GitHub CI (Or I guess any CI) is to change your build OS to windows. I'm using windows-latestand it seems to build fine. Will update with any more info I get.

pippinmole · 2025-02-07T21:07:53Z

So, I've done some further investigating...

What I did was work my way from a fresh install, slowly copying things over until something broke:

Create a new testing branch
Deleted my entire chrome extension
Created an entirely new one with src directory
At this point, it broke
Delete styles.css and its import from newtab.tsx (line 3)
This works

Not very helpful, since we all need stylesheets I assume. For now I'm just going to build on windows and hope that the devs pick this project back up

osarhan · 2025-02-07T21:22:37Z

@pippinmole lets go! This worked for me!

At this point, im not interested in investigating more, since I have a working pipeline now. I appreciate you digging into this! 💪

lucasrui · 2025-02-19T08:29:23Z

Short term fix for GitHub CI (Or I guess any CI) is to change your build OS to windows. I'm using windows-latestand it seems to build fine. Will update with any more info I get.

this works for me too! can you share your yaml in GitHub CI?
here is my yaml,

name: "Submit to Web Store"
on:
  workflow_dispatch:

jobs:
  build:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v3
      - name: Cache pnpm modules
        uses: actions/cache@v3
        with:
          path: ~/.pnpm-store
          key: ${{ runner.os }}-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: |
            ${{ runner.os }}-
      - uses: pnpm/action-setup@v4
        with:
          run_install: true
      - name: Use Node.js 22.x
        uses: actions/[email protected]
        with:
          node-version: 22.13.0
          cache: "pnpm"
      - name: Build the extension
        run: pnpm build
      - name: Package the extension into a zip artifact
        run: pnpm package
      - name: Browser Platform Publish
        uses: PlasmoHQ/bpp@v3
        with:
          keys: ${{ secrets.SUBMIT_KEYS }}
          artifact: build/chrome-mv3-prod.zip

node version:22.13.0
pnpm version:9.15.3
plasmo version:0.90.3

I face the same error as "Segmentation fault (core dumped)", when I runs-on ubuntu-latest

pippinmole · 2025-02-19T14:45:12Z

Hi everybody,

Unfortunately it looks like this is an upstream issue on the latest version of Parcel, which is a package we use. We may have to wait until parcel-bundler/parcel#10081 is noticed by the devs and fixed. Sorry for the inconvenience.

osarhan · 2025-02-19T19:41:41Z

@pippinmole Is there a parcel version we can pin in our plasmo projects to unbreak the build?

jeffminim · 2025-02-20T08:35:20Z

Hi everybody,

Unfortunately it looks like this is an upstream issue on the latest version of Parcel, which is a package we use. We may have to wait until parcel-bundler/parcel#10081 is noticed by the devs and fixed. Sorry for the inconvenience.

Encountering the same issue. Running directly under terminal without using Github CI will also report errors.
I've troubleshooted it and I feel that the problem occurs when compiling the css.

DenizUgur added the bug Something isn't working label Jan 13, 2025

This was referenced Feb 19, 2025

[BUG] Segmentation fault during build #1089

Closed

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

Closed

"Segmentation fault (core dumped)" from GitHub Actions parcel-bundler/parcel#10081

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[BUG] TailwindCSS example does not build #1156

[BUG] TailwindCSS example does not build #1156

DenizUgur commented Jan 13, 2025 •

edited

Loading

gregoryPacific commented Jan 14, 2025

spiceworm commented Jan 15, 2025

detronetdip commented Jan 23, 2025

gregoryPacific commented Jan 23, 2025

ahmedazizkhelifi commented Feb 3, 2025 •

edited

Loading

osarhan commented Feb 3, 2025 •

edited

Loading

osarhan commented Feb 6, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025 •

edited

Loading

ahmedazizkhelifi commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

ahmedazizkhelifi commented Feb 7, 2025

osarhan commented Feb 7, 2025

pippinmole commented Feb 7, 2025

pippinmole commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

lucasrui commented Feb 19, 2025

pippinmole commented Feb 19, 2025

osarhan commented Feb 19, 2025

jeffminim commented Feb 20, 2025

[BUG] TailwindCSS example does not build #1156

[BUG] TailwindCSS example does not build #1156

Comments

DenizUgur commented Jan 13, 2025 • edited Loading

What happened?

Version

What OS are you seeing the problem on?

What browsers are you seeing the problem on?

Relevant log output

(OPTIONAL) Contribution

Code of Conduct

gregoryPacific commented Jan 14, 2025

Version

What OS are you seeing the problem on?

Relevant log output:

spiceworm commented Jan 15, 2025

detronetdip commented Jan 23, 2025

gregoryPacific commented Jan 23, 2025

ahmedazizkhelifi commented Feb 3, 2025 • edited Loading

osarhan commented Feb 3, 2025 • edited Loading

osarhan commented Feb 6, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025 • edited Loading

ahmedazizkhelifi commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

ahmedazizkhelifi commented Feb 7, 2025

osarhan commented Feb 7, 2025

pippinmole commented Feb 7, 2025

pippinmole commented Feb 7, 2025

pippinmole commented Feb 7, 2025

osarhan commented Feb 7, 2025

lucasrui commented Feb 19, 2025

pippinmole commented Feb 19, 2025

osarhan commented Feb 19, 2025

jeffminim commented Feb 20, 2025

DenizUgur commented Jan 13, 2025 •

edited

Loading

ahmedazizkhelifi commented Feb 3, 2025 •

edited

Loading

osarhan commented Feb 3, 2025 •

edited

Loading

osarhan commented Feb 7, 2025 •

edited

Loading