ffmpegwasm / ffmpegwasm/ffmpeg.wasm

Manually provide `814.ffmpeg.js`'s path

Open
#688 4 comments 1 reaction 0 assignees View on GitHub
Dominant language
C
Stars
17.8k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
I cannot load the module in a Chrome extension scaffolded by [Plasmo](/plasmohq/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](/parcel-bundler/parcel) under the hood, renames the file to include a hash, e.g. `814.ffmpeg.d7h8ng.js`

**Describe the solution you'd like**
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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.