node-modern

Enforce modern Node.js 22+ patterns in TypeScript projects.

224|27|Updated May 12, 2026
One-click install
npx skills add https://github.com/WrongStack/WrongStack --skill node-modern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-modern
Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/node-modern
Command: npx skills add https://github.com/WrongStack/WrongStack --skill node-modern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Node.js 22+ projects often struggle with inconsistent module systems, lack of native fetch usage, and asynchronous patterns that cause subtle bugs. This skill provides a clear set of practices and conventions to adopt modern Node.js development, reduce runtime errors, and improve maintainability across teams.

Core Features & Use Cases

  • ESM-first guidance and projects migration for Node.js 22+ codebases.
  • Enforce use of node: protocol for built-ins and native fetch with AbortSignal.
  • Provide patterns for robust async code, error handling, and progressive migration workflows.

Quick Start

Use this skill to audit a codebase for modern Node.js patterns and apply recommended changes in a single pass.

Frequently Asked Questions about node-modern

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

FAQPage Schema
How do I migrate a TypeScript project to ESM in Node.js 22?▼

To migrate a TypeScript project to ESM in Node.js 22, configure your codebase around ESModule imports, enforce the node: protocol for built-ins, and apply progressive migration workflows to ensure consistent module systems and reduce runtime errors.

What is the best way to handle async errors in modern Node.js?▼

The best way to handle async errors in modern Node.js is to adopt all-Settled async patterns and implement proper error handling for ENOENT, which reduces subtle runtime bugs and improves overall codebase maintainability.

How do I use native fetch with AbortSignal in Node.js?▼

Using native fetch with AbortSignal in Node.js 22+ replaces external HTTP libraries by leveraging built-in APIs for request cancellation. This modern pattern requires a codebase structured around ESModule imports to function correctly.

Does this modern Node.js approach work with existing TypeScript projects?▼

Modern Node.js patterns work with existing TypeScript projects through progressive migration workflows designed for refactoring and onboarding. It requires Node.js 22+ and applies to repos actively transitioning to ESM, node: protocol, and native fetch.

Why should I enforce the node: protocol in Node.js 22?▼

Enforcing the node: protocol in Node.js 22 explicitly differentiates built-in core modules from third-party packages. This practice prevents module resolution ambiguity in ESM-first projects and ensures consistent loading behavior across the codebase.