migrate-to-v5

Upgrade gluestack-ui projects to v5 using the gluestack-ui CLI.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jia-wei-00/expense-tracker --skill migrate-to-v5-jia-wei-00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-v5
Source: https://github.com/jia-wei-00/expense-tracker/tree/main/.agents/skills/gluestack-ui-v4/migrate-to-v5
Command: npx skills add https://github.com/jia-wei-00/expense-tracker --skill migrate-to-v5-jia-wei-00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating gluestack-ui projects to version 5 with both automated CLI upgrades and a guided manual path.

Core Features & Use Cases

  • Automated upgrade: uses the gluestack-ui CLI to migrate project dependencies, config, and scaffolding to v5.
  • Dual-path support: handles NativeWind v5 and UniWind migration paths for v4+ projects, plus legacy v2/v3 cases.
  • Practical guidance: provides step-by-step instructions and validation steps for a safe, reproducible migration.

Quick Start

Run the upgrade wizard with npx gluestack-ui@alpha upgrade from the project root.

Frequently Asked Questions about migrate-to-v5

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

FAQPage Schema
How do I migrate gluestack-ui to v5?

Migrate gluestack-ui to v5 by running the npx gluestack-ui@alpha upgrade wizard from your project root to automate dependency updates, config migrations, and provider re-addition.

Can I migrate gluestack-ui v2 or v3 projects to v5?

Yes, the gluestack-ui v5 migration handles projects on v2, v3, or v4, using a guided path for legacy versions and automated CLI tooling for newer setups.

Does the gluestack-ui v5 migration support NativeWind and UniWind?

Yes, gluestack-ui v5 migration supports both NativeWind v5 and UniWind workflows across Expo and React Native setups with coordinated package updates and config migrations.

What configuration changes are required for a gluestack-ui v5 upgrade?

The gluestack-ui v5 upgrade requires config migrations for tailwind, metro, and babel, alongside coordinated package updates and provider re-addition steps.

Why does my gluestack-ui upgrade to v5 require manual steps?

The gluestack-ui v5 upgrade includes manual steps because the guided migration path provides validation steps and instructions to ensure a safe, reproducible migration across different setups.