react-vendoring

To enforce safe vendoring boundaries for React in Next.js, ensure all react-server-dom-webpack/* imports pass through entry-base.ts and comply with ESLint rules to maintain correct react-server workflow separation.

Turbopack remap breaks during react-server boundary updates occur when imports bypass entry-base.ts. Route all react-server-dom-webpack/* imports through this boundary file to prevent runtime issues and maintain remap stability.

ESLint suppression guidelines for vendored React code dictate applying boundary rules to entry-base.ts modifications. Proper suppression prevents runtime issues while ensuring react-server-dom-webpack/* imports comply with Turbopack remap behavior and type declarations.

Updating App Router vendoring involves modifying taskfile.js when adjusting react-server boundaries. This ensures correct handling of vendored React channels, type declarations, and entry-base.ts boundary rules within the Next.js react-server workflow.

Importing react-server-dom-webpack/* directly without entry-base.ts violates vendoring boundary control. You must pass these imports through entry-base.ts to comply with ESLint rules and ensure correct Turbopack remap behavior in Next.js.

React-server vendoring is the process of managing internal React code boundaries for Next.js's react-server layer. You need to manage these boundaries when editing entry-base.ts, updating type declarations, or modifying react-server-dom-webpack channels to prevent runtime issues.