react-icons 5.x

Use react-icons v5 icon-pack subpath imports, core component types, context, and documented packaging boundaries without relying on obsolete pre-v3 imports or unavailable manifest paths.

For

react-icons@5.7.0

Verified

2026-09-07, 3 examples executed

Package

@modootoday/pmcp-react-icons@5.0.0

What it covers

• Version and package boundary
• Import icons from an icon-pack subpath
• Common import mistake
• Standalone import check
• Core component API
• Global icon context
• Manifest declarations and runtime path
• Installation and packaging notes
• What this skill does not cover

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 { createElement } from "react";
import { FaBeer } from "react-icons/fa";

assert.equal(typeof FaBeer, "function");

const element = createElement(FaBeer, { title: "Beer" });
assert.equal(element.type, FaBeer);
assert.equal(element.props.title, "Beer");

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-icons

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