What problem does it solve?
React vendoring and react-server layer boundaries introduce complexity in module resolution and surface area when editing vendored React code. This skill provides a structured approach to ensure changes go through the correct boundary points and maintain consistent behavior across App Router and server components.
Core Features & Use Cases
- App Router Vendoring: vendored React channels (stable and experimental) are wired to Turbopack aliases; Pages Router resolves React from node_modules for standard cases.
- Entry-base.ts Boundary: all react-server-dom-webpack/* imports must go through entry-base.ts; ensure safe access to Flight APIs via ComponentMod.
- Type Declarations: update $$compiled.internal.d.ts to reflect new APIs; keep type surface in sync with vendored React.
- ESLint Practical Rule: apply scoped disable/enable for dynamic requires to avoid lint/backwards compatibility issues.
- Turbopack Remap: understand that Turbopack remaps the import to turbopack variants at runtime.
- Use Case: apply this skill when editing vendored React or react-server layer boundaries to ensure correct module resolution and safe access to server APIs.
Quick Start
Apply changes to vendored React only through entry-base.ts and validate that all react-server-dom-webpack imports route via the React boundary.