ffmpegwasm/ffmpeg.wasm

in umi，ffmpeg.load fail，indicate Error: Cannot find module

Open

#552 opened on Aug 16, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C (17,474 stars) (1,071 forks)batch import
help wanted

Description

Describe the bug

in umi，ffmpeg.load fail，indicate:

Uncaught (in promise) Error: Cannot find module 'blob:http://127.0.0.1:8001/594fd908-516c-4e5e-9160-02a0b11302f5' at node_modules_ffmpeg_ffmpeg_dist_esm_lazy_recursive.js:14:11

To Reproduce Please provide a GitHub link or code snippet.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots image image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context Add any other context about the problem here.

Contributor guide

Tech stack
javascriptwasm
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaScriptWebAssembly basicsffmpeg.wasm usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the module loading mechanism in ffmpeg.wasm, particularly the lazy loading of the WebAssembly binary. Check if the import() call fails due to incorrect base URL or missing polyfill. Look at the source of `node modules ffmpeg ffmpeg dist esm lazy recursive.js` to understand how modules are loaded. Ensure that the WebAssembly binary is properly served and accessible. Possibly need to verify the browser environment (e.g., CORS, same origin policy). Try to reproduce with a minimal setup using a bundler like webpack or vite.