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] Can't use ffmpeg #1128

Open
2 of 3 tasks
llllash opened this issue Nov 8, 2024 · 0 comments
Open
2 of 3 tasks

[BUG] Can't use ffmpeg #1128

llllash opened this issue Nov 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@llllash
Copy link

llllash commented Nov 8, 2024

What happened?

Is your feature request related to a problem? Please describe.
I cannot load the module in a Chrome extension scaffolded by Plasmo
The reason is that when FFmpeg loads up, it looks for 814.ffmpeg.js in the same directory as ffmpeg.js, whereas Plasmo, which uses Parcel under the hood, renames the file to include a hash, e.g. 814.ffmpeg.d7h8ng.js

Describe the solution you'd like
Provide methods not to rename files to include hashes Or Get a Allow manually providing a path to 814.ffmpeg.js

Describe alternatives you've considered
The only alternative is to create an extension without using Plasmo

Version

Latest

What OS are you seeing the problem on?

No response

What browsers are you seeing the problem on?

No response

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.
@llllash llllash added the bug Something isn't working label Nov 8, 2024
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

1 participant