plasmo icon indicating copy to clipboard operation
plasmo copied to clipboard

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

Open Eve-Sama opened this issue 1 year ago • 8 comments

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

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

Eve-Sama avatar Jan 06 '25 09:01 Eve-Sama

Is there a solution?

027xiguapi avatar Jan 07 '25 03:01 027xiguapi

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

GeekEast avatar Jan 08 '25 06:01 GeekEast

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

bennyli519 avatar Jan 08 '25 06:01 bennyli519

I'm having the same problem.

axin7 avatar Jan 13 '25 14:01 axin7

I'm having the same problem.

A month has passed and this problem still exists

axin7 avatar Feb 14 '25 10:02 axin7

The same problem. I have to import the one for Chrome into Edge (they should be fully compatible). But, please repair this bug.

jeffminim avatar Feb 20 '25 08:02 jeffminim

just run into the same issue when publishing to edge. Is there any workaround to exclude these manually?

onmomo avatar Apr 09 '25 14:04 onmomo

just run into the same issue when publishing to edge. is there any workaround to exclude these manually?

I manually removed the edge error from the manifest.json and then manually compressed it before uploading it

axin7 avatar Apr 09 '25 14:04 axin7