Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Why build manifest contains non-existent css files #1153

Open
2 of 3 tasks
Eve-Sama opened this issue Jan 6, 2025 · 3 comments
Open
2 of 3 tasks

[BUG] Why build manifest contains non-existent css files #1153

Eve-Sama opened this issue Jan 6, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@Eve-Sama
Copy link

Eve-Sama commented Jan 6, 2025

What happened?

When I execute below command

npx plasmo build --target=edge-mv3 --env=.env.custom.edge

.env.custom.edge

PLASMO_PUBLIC_PLATFORM="edge"

Then I discovered content.66d1ff77.css and content.f5c813fc.css, the files not exist in build directory.

图片

What am I suppose to do to avoid this situation.

Version

Latest

What OS are you seeing the problem on?

MacOSX

What browsers are you seeing the problem on?

Microsoft Edge

Relevant log output

No response

(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.
@Eve-Sama Eve-Sama added the bug Something isn't working label Jan 6, 2025
@027xiguapi
Copy link

Is there a solution?

@GeekEast
Copy link

GeekEast commented Jan 8, 2025

We found the same issue here and the extension cannot pass the edge store validation check now.

@bennyli519
Copy link

Is there a solution?
currently using Style Raw text As a temporary solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants