fix(nuxthub): skip build-time dump handoff for local databases

[benjamincanac]

🔗 Linked issue

Resolves #3821 (second part, see also nuxt/nuxt.com#2358)

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Stacked on #3822.

When applyMigrationsDuringBuild is enabled, setupNitro() hands the content dump to hub's build-time migrations and disables the runtime integrity check, assuming the migrated database is the one the runtime will use. That only holds for remote databases. For a local file: database the migrated file is discarded with the build machine, so the runtime database starts empty and the disabled integrity check prevents the runtime dump import. Collections come back empty, which is why nuxt.com has to set applyMigrationsDuringBuild: false.

The handoff is now gated on the resolved database being remote (d1, postgresql, or libsql with a non-file: URL). For local file: libsql databases the handoff is skipped and integrityCheck stays true, including URLs already on file:/tmp/ which previously skipped the rewrite block and kept integrityCheck: false, the exact empty-collections trap.

Added unit tests covering the skipped handoff for local databases (including the file:/tmp/ case) and the performed handoff with disabled integrity check for a remote database.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
content	Ready	Preview	Jul 30, 2026 3:17pm