What problem does it solve? Editing vendored React code in the Next.js codebase is error-prone: direct imports from react-server-dom-webpack outside entry-base.ts fail at runtime, type declarations live in a non-obvious file, and Turbopack silently remaps packages. This Skill encodes those rules so changes compile and run correctly. ## Core Features & Use Cases - Entry-base boundary enforcement: Explains that all react-server-dom-webpack/* imports must go through entry-base.ts, with other files accessing Flight APIs via the ComponentMod parameter. - Type declaration workflow: Shows how to add declare module blocks in packages/next/types/$$compiled.internal.d.ts when exposing new APIs like renderToPipeableStream. - Vendoring and channel knowledge: Covers the copy_vendor_react task in taskfile.js, stable vs experimental channels in compiled/react*, and Turbopack's remap to react-server-dom-turbopack. - Use Case: When adding a Node.js-only React API such as prerenderToNodeStream, follow the documented steps: add the type declaration, export it from entry-base.ts behind a process.env guard, and consume it through ComponentMod. ## Quick Start Ask how to safely add a new react-server-dom-webpack server.node API to the Next.js App Router build.
