Codex skills for Node.js

Node.js skills cover the server frameworks (Express 5, Fastify, NestJS, Hono) and the runtime under them: streams, event loop profiling, memory leaks, Bun and ESM. Codex structures services so their tests run offline through Supertest or app.inject, keeps memory flat on large inputs with stream pipelines, and profiles under realistic load before it changes code.

Every Node.js skill in one command

Installs these 15 into ~/.agents/skills/. Add --project after -- to install into the current repository instead.

The installer is a 104-line POSIX shell script. It fetches the skills you name from codexskills.dev and unpacks each into its own folder in your skills directory. No sudo, no telemetry, and every skill page shows the full SKILL.md first. Read install.sh

curl -fsSL codexskills.dev/install.sh | sh -s -- node-streams node-profiling express-api fastify-api hono-edge-api bun-runtime nestjs-modules codex-sdk-automation session-auth node-esm-migration llm-streaming cors-configuration memory-leak-hunting dependency-injection cli-tool-building

Node.js FAQ

Is there a Codex skill for upgrading Express 4 to Express 5?

Express 5 API includes a migration reference for the Express 4 traps: path-to-regexp v8 wildcards that reject app.get('*'), the read-only req.query getter and removed methods. Because Express 5 forwards rejected promises to the error handler, it drops express-async-errors and manual try/catch wrappers, validates input with Zod and covers each route's failure modes with Supertest.

How does Codex find what is blocking the Node.js event loop?

Node.js Profiling first decides whether the service is CPU-bound, blocking the loop, waiting on I/O or leaking, using perf_hooks event loop utilisation and the monitorEventLoopDelay histogram. It then captures the matching profile under realistic load with --cpu-prof, the inspector, heap profiles, 0x or Clinic.js, names the hot function and re-runs the same load to prove the fix. For memory that only grows, Memory Leak Hunting uses the three-snapshot technique and the retainer path.

Can Codex move a Node project to Bun?

Bun Runtime adopts Bun one layer at a time: package manager, then tests, then runtime. It commits the text bun.lock, lists trustedDependencies for packages that need postinstall, and keeps tsc in CI because Bun strips types without checking them. It also warns that bun run still executes tools with a node shebang on Node unless you pass --bun.

How do I install all 15 Node.js skills at once?

Pass every name to the installer in one command: curl -fsSL https://codexskills.dev/install.sh | sh -s -- node-streams node-profiling express-api fastify-api hono-edge-api bun-runtime nestjs-modules codex-sdk-automation session-auth node-esm-migration llm-streaming cors-configuration memory-leak-hunting dependency-injection cli-tool-building. Add --project right after -- to put them in the current repository's .agents/skills/ so your team gets them too.

Which Node.js skill should I try first?

Node.js Streams is the closest fit for most Node.js work. Mention it with $node-streams in a prompt to load it on purpose; after that, Codex picks it up on its own whenever a task matches.

esc