dextinity-major-migration

Migrates Dextinity projects across major versions following official migration guides.

52|9|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-major-migration-vivid-planet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dextinity-major-migration
Source: https://github.com/vivid-planet/dextinity/tree/main/skills/dextinity-major-migration
Command: npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-major-migration-vivid-planet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading @dextinity/* packages across a major version involves breaking changes across React, Next.js, and MUI X, plus codemods, config updates, and runtime regressions that lint and tsc cannot catch. This Skill orchestrates the entire migration so no guide step, site, or verification pass is missed. ## Core Features & Use Cases - Guide-driven migration: Locates the official Dextinity migration guide for the target major, resolves the newest stable release within that major, and works through every section with per-section commits. - Project shape detection: Discovers whether the project has zero, one, or multiple sites and whether a page tree exists, then applies site-specific steps once per site. - Independent audit and smoke test: Verifies the migration with a fresh subagent cross-referencing commits against the guide, then runs a Playwright-driven browser smoke test of admin routes, page-tree CRUD, and site URLs. - Use Case: You need to upgrade a Dextinity project from v5 to v6 with two sites. The Skill downloads the official guide, bumps all @dextinity/* packages to the latest v6 release, applies each section per site, commits incrementally, and produces a test-report.md of browser-verified findings. ## Quick Start Migrate this project from Dextinity v5 to v6 following the official migration guide.

Frequently Asked Questions about dextinity-major-migration

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

FAQPage Schema
How do I upgrade Dextinity to a new major version?

Download the official migration guide for your target major from the Dextinity repository, bump all @dextinity/* packages to the newest stable release within that major, then apply each guide section in order with per-section commits and lint verification.

How do I migrate a Dextinity project with multiple sites?

Detect sites by scanning package.json files for @dextinity/site-nextjs, then run every site-specific guide step once per site. Each site has its own package.json, config, and dev port, so skipping duplicates is the most common multi-site migration mistake.

Should I pin Dextinity packages to the .0.0 release of a new major?

No. The .0.0 release lacks later bug fixes, so pin every core @dextinity/* package to the newest stable minor or patch within the target major. Use npm view to list versions and filter out pre-releases like canary, beta, or rc.

Why does my Dextinity migration pass tsc but break at runtime?

Hand-written types can mask runtime changes, such as a synchronous type over a value that is now a Promise. When a guide step makes an API async, manually scan every affected file in every site instead of trusting tsc or lint to flag them.

What should I do when a Dextinity codemod or npm install fails during migration?

Stop immediately and hand the exact failing command to the user rather than working around it. This applies to npm install failures, codemod errors, and sandbox-blocked commands; resume from the same step after the user confirms.

When should I not use a major migration workflow for Dextinity?

Do not use it for minor or patch upgrades, or for ongoing feature work on a project already on the target major. It is designed only for cross-major upgrades that follow an official migration guide.