Skip to content
TrustedSkillsbeta
Back to all skills

React Vendoring

Official
vercel·vlatest·frontend·MIT

Dynamically fetch and render Vercel edge functions as components in your React applications for optimized data delivery.

Repository

Install on your platform

This skill no longer installs under the name react-vendoring. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

vercel

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned vercel/next.js at e7feae7d53.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e7feae7d53
Manifest
.agents/skills/react-vendoring/SKILL.md
Scanned
1 file, 71 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, react-vendoring, facilitates changes related to vendored React code within Next.js applications. Specifically, it addresses how React is handled in the App Router (where it's not resolved from node_modules but is instead vendored) and provides guidance on working with server components and APIs from react-server-dom-webpack/*. It ensures proper integration of these components while avoiding runtime errors related to incorrect import paths or missing type declarations.

When to use it

  • When modifying React code that's been vendored as part of a Next.js project (particularly with the App Router).
  • When integrating new APIs from react-server-dom-webpack/* into your application’s server components.
  • If you encounter runtime errors indicating "The react-server condition must be enabled" when working with React server features.
  • When adding Node.js-only React APIs to your Next.js project.

Key capabilities

  • Provides guidance on managing React versions in the App Router versus the Pages Router.
  • Details how to handle stable and experimental React channels (compiled/react/ and compiled/react-experimental/).
  • Explains the importance of importing Flight server APIs through entry-base.ts.
  • Outlines the process for adding type declarations for new React APIs in $$compiled.internal.d.ts.
  • Describes how to safely expose Node.js-only React APIs using environment variables and the ComponentMod parameter.

Example prompts

  • "How do I add a new API from react-server-dom-webpack/*?"
  • "Why am I getting an error saying 'The react-server condition must be enabled'?"
  • "Where should I put type declarations for vendored React packages?"

Tips & gotchas

  • App Router Specific: The skill is most relevant when working with the Next.js App Router, as React handling differs significantly from the Pages Router.
  • entry-base.ts is Key: All imports from react-server-dom-webpack/* must go through entry-base.ts in the (react-server) layer to avoid runtime errors.
  • Type Declarations are Required: Always add type declarations for new React APIs to packages/next/types/$$compiled.internal.d.ts.