Does this skill support the Fastify framework?

Yes, the implementation examples are specifically optimized for Fastify, though the architectural principles can be adapted to any Node.js framework like Express or NestJS.

Which API versioning strategy is recommended?

URL path versioning (e.g., /api/v1) is generally recommended because it is the most explicit, easiest to test, and provides the best results for web caching.

What is the difference between breaking and non-breaking changes?

Non-breaking changes include adding optional fields or new endpoints. Breaking changes involve removing or renaming fields, which this skill helps manage through new version releases.

How do I handle API deprecation with this skill?

The skill includes a deprecation plugin pattern that automatically adds 'Deprecation' and 'Sunset' headers to responses, informing clients of upcoming end-of-life dates.

API Versioning for Node.js

Name: API Versioning for Node.js
Author: IvanTorresEdge

byIvanTorresEdge

API Development

Implements robust API versioning strategies and deprecation patterns for Node.js backends to ensure long-term backward compatibility.

About

This skill provides a comprehensive set of patterns and implementations for managing API evolution in Node.js applications. It guides developers through selecting and implementing the most effective versioning strategies—including URL path, header-based, and query parameter methods. Beyond simple routing, it offers advanced patterns for version-specific response transformers, Zod-based schema validation, and automated deprecation handling using standardized HTTP headers like Sunset and Link. It is an essential tool for teams building public APIs or microservices that must support multiple client versions simultaneously.

Key Features

Versioned response transformers and Zod schema validation
Multiple versioning strategies (URL, Header, and Query Param)
Standardized version routing patterns for clean code organization
Guidance on breaking vs. non-breaking change management
Automated deprecation and sunset header management
0 GitHub stars

Use Cases

Migrating legacy backend services to modern data structures without breaking existing clients
Building public-facing REST APIs requiring high stability and backward compatibility
Managing complex API lifecycles with clear deprecation and sunsetting roadmaps

About

Key Features

Versioned response transformers and Zod schema validation
Multiple versioning strategies (URL, Header, and Query Param)
Standardized version routing patterns for clean code organization
Guidance on breaking vs. non-breaking change management
Automated deprecation and sunset header management
0 GitHub stars

Use Cases

Migrating legacy backend services to modern data structures without breaking existing clients
Building public-facing REST APIs requiring high stability and backward compatibility
Managing complex API lifecycles with clear deprecation and sunsetting roadmaps