nuxthub-migration

Migrate NuxtHub projects to Cloudflare Workers with Wrangler bindings.

5|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/onmax/nuxthub-v1-skill --skill nuxthub-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuxthub-migration
Source: https://github.com/onmax/nuxthub-v1-skill/tree/main
Command: npx skills add https://github.com/onmax/nuxthub-v1-skill --skill nuxthub-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from migrating NuxtHub applications away from the legacy NuxtHub Admin and GitHub Actions deployment flow, while preserving existing data and deployment continuity.

Core Features & Use Cases

  • Legacy self-hosting migration: Rebuilds a project for Cloudflare Workers with Wrangler bindings and Workers Builds while keeping the existing application code unchanged.
  • v0.10 and nightly upgrade path: Guides the move from database: true to db-based configuration, and updates database, KV, and blob access patterns to the newer virtual module APIs.
  • Cloud resource preservation: Helps reuse existing D1, KV, and R2 resources so migrations do not accidentally wipe production data.
  • Use case: A team with an older NuxtHub app can use this Skill to remove the deprecated deployment pipeline, configure wrangler.jsonc, and then refactor the app for the newer multi-cloud architecture.

Quick Start

Ask the assistant to audit this NuxtHub project and migrate it according to the appropriate phase, including Wrangler configuration, deployment cleanup, and any required v0.10 API updates.

Frequently Asked Questions about nuxthub-migration

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

FAQPage Schema
How do I migrate NuxtHub from legacy GitHub Actions to self-hosted Cloudflare Workers?

Migrate NuxtHub to Cloudflare Workers by configuring Wrangler bindings and Workers Builds, which rebuilds the project for self-hosting while keeping existing application code unchanged and preserving deployment continuity.

How do I upgrade NuxtHub to v0.10 without breaking database and blob access?

Upgrade NuxtHub to v0.10 by moving from the database: true configuration to db-based settings, and updating database, KV, and blob access patterns to use the newer virtual module APIs.

Can I migrate NuxtHub to Wrangler bindings without losing existing D1, KV, and R2 data?

Yes, NuxtHub migration preserves existing Cloudflare resources by reusing current D1, KV, and R2 bindings, ensuring migrations do not accidentally wipe production data during the deployment transition.

What's the best way to configure wrangler.jsonc for a NuxtHub multi-cloud deployment?

Configure wrangler.jsonc by setting up cloudflare_module deployment settings and defining Wrangler bindings, which removes the deprecated NuxtHub Admin pipeline and refactors the app for modern multi-cloud architecture.

When do I need to replace NuxtHub database APIs with virtual module APIs?

Replace NuxtHub database APIs with virtual module APIs when upgrading to v0.10 or nightly builds, transitioning away from legacy patterns to db-based configurations for database, KV, and blob access.