# wasp-lang/wasp · RepoSense Release & Migration Intelligence

> Ships `@wasp-lang/wasp@0.26.1` with upstream runtime refin. Review breaking API changes before up… Migration: Moderate.

## Metadata
- **Repository URL**: https://github.com/wasp-lang/wasp
- **Primary Package**: `@wasp-lang/wasp` (NPM)
- **Categories**: `FRAMEWORK`, `BACKEND`
- **Latest Version**: `v0.26.1`
- **Semantic Status**: `BREAKING`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/wasp-lang/wasp/releases.atom

## The Human Context (Plain-English Pitch)
@wasp-lang/wasp is an open-source library and developer tool in the wasp-lang/wasp ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
Ships `@wasp-lang/wasp@0.26.1` with upstream runtime refin. Review breaking API changes before up… Migration: Moderate.

## Breaking Changes & Required Actions
- [BREAKING] Wasp now requires Node.js >=24.22.1 (previously >=24.14.1), which includes fixes for the October 2026 Node.js security vulnerabilities. (#5113)
- Ships `@wasp-lang/wasp@0.26.1` with upstream runtime refinements and stability fixes from `wasp-lang/wasp`.
- Updates TypeScript declarations and internal module exports for `v0.26.1`.

## Migration Snippet
```ts
npm install @wasp-lang/wasp@0.26.1
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v0.26.1** (2026-10-23) [BREAKING]: Ships `@wasp-lang/wasp@0.26.1` with upstream runtime refin. Review breaking API changes before up… Migration: Moderate.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is wasp-lang/wasp v0.26.1 safe to upgrade in production?
wasp-lang/wasp v0.26.1 is classified as BREAKING (PATCH release). Ships `@wasp-lang/wasp@0.26.1` with upstream runtime refin. Review breaking API changes before up… Migration: Moderate.

### What breaking changes or compatibility risks exist in wasp-lang/wasp v0.26.1?
Wasp now requires Node.js >=24.22.1 (previously >=24.14.1), which includes fixes for the October 2026 Node.js security vulnerabilities. (#5113)

### What is the bundle size impact of @wasp-lang/wasp v0.26.1?
Measured bundle size telemetry is currently unavailable for @wasp-lang/wasp v0.26.1; verify build output locally before deploying.

### How do I upgrade @wasp-lang/wasp to v0.26.1?
Upgrade @wasp-lang/wasp to v0.26.1 by running "npm install @wasp-lang/wasp@0.26.1" and applying the migration steps: npm install @wasp-lang/wasp@0.26.1