Skip to content

docs(contributing): document Next.js 16 --webpack requirement for FFmpeg.wasm #1821

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.

Sign up for GitHub

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

Open
chiragjangiir wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(contributing): document Next.js 16 --webpack requirement for FFmpeg.wasm #1821

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,6 +224,22 @@ Environment variables guide: https://nextjs.org/docs/app/guides/environment-vari

---

### 9. Webpack Requirement for Next.js 16 (`--webpack`)
The `dev` and `build` scripts in `package.json` explicitly include the `--webpack` flag:

```json
"dev": "next dev --webpack",
"build": "next build --webpack"
```

**Why this is required:**
Next.js 16 defaults to Turbopack. However, `next.config.ts` configures a custom Webpack fallback (`config.resolve.fallback = { fs: false }`) which is strictly required for FFmpeg.wasm (`@ffmpeg/ffmpeg`) to load WebAssembly files properly. Turbopack ignores this Webpack configuration block.

**Important:**
Do not remove `--webpack` from the scripts in `package.json`. Removing this flag causes Next.js to run with Turbopack, which will silently bypass the required Webpack fallback and break FFmpeg WebAssembly loading.

---

## Finding Issues

We have **300+ open issues** across all skill levels:
Expand Down
Loading