react-dom 19.x

Use react-dom ^19.0.0 with React 19 root, server-rendering, portal, scheduling, form-status, and resource APIs. Avoid removed React 18-era entry points and distinguish browser-only APIs from standalone server APIs.

For

react-dom@19.2.8

Verified

2026-09-07, 2 examples executed

Package

@modootoday/pmcp-react-dom@19.0.0

What it covers

• Scope
• React 19 root APIs
• Common outdated shapes
• Server rendering
• Browser APIs from `react-dom`
• Forms and React 19 additions
• Features requiring tooling or framework integration
• Does not cover
• Sources

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict';
import React from 'react';
import { renderToString } from 'react-dom/server';

const markup = renderToString(
  React.createElement('main', null, React.createElement('h1', null, 'Hello')),
);

assert.match(markup, /<main>/);
assert.match(markup, /<h1>Hello<\/h1>/);

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-react-dom

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.