From c442eaacdeee19af7904e790871ca8e3a9c0f5e8 Mon Sep 17 00:00:00 2001
From: Chirag Jangir <184008125+chiragjangiir@users.noreply.github.com>
Date: Wed, 21 Oct 2026 16:09:35 +0530
Subject: [PATCH] docs(contributing): document Next.js 16 --webpack flag
 requirement

---
 CONTRIBUTING.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2534f84d0..839d33133 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -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: