react-vendoring

Enforce React vendoring boundaries through entry-base.ts in Next.js react-server workflows.

Updated Apr 7, 2026

Search Tags:#eslint #turbopack #entry-base #vendored-react #react-server-dom-webpack #types-declarations

Ready to run

npx skills add https://github.com/villa1/backupshop --skill react-vendoring-villa1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: react-vendoring
Source: https://github.com/villa1/backupshop/tree/main/.agents/skills/react-vendoring
Command: npx skills add https://github.com/villa1/backupshop --skill react-vendoring-villa1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

React vendoring and boundary enforcement for the react-server layer in Next.js, ensuring correct handling of vendored React code, channels, and type declarations.

Core Features & Use Cases

Vendoring boundaries for React, ensuring all react-server-dom-webpack/* imports pass through entry-base.ts
Clear guidance for App Router vendoring, entry-base boundary rules, and type declarations
ESLint suppression guidelines and Turbopack remap considerations to prevent runtime issues

Quick Start

Edit entry-base.ts and related react-server code when modifying vendored React to ensure boundary correctness and proper channel usage.

Frequently Asked Questions about react-vendoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce safe vendoring boundaries for React in Next.js?▼

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.

Why does my Turbopack remap break when updating react-server boundaries?▼

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.

What are the ESLint suppression guidelines for vendored React code?▼

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.

Do I need to modify taskfile.js when updating App Router vendoring?▼

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.

Can I import react-server-dom-webpack directly without using entry-base.ts?▼

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.

What is react-server vendoring and when do I need to manage its boundaries?▼

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.