Limits: Rollback of Database Schema Changes Not Supported in StackBlitz

Rollback of Schema Changes in StackBlitz

Developers who use StackBlitz for rapid front‑end prototyping often need to experiment with a lightweight database, such as IndexedDB, SQLite, or an external service. When a schema change is applied, the platform provides no native mechanism to revert that change automatically.

The core constraint is that StackBlitz’s back‑end persistence is limited to local storage or external services; it does not expose a migration API or a version‑controlled schema store. Consequently, any schema alteration must be undone manually or by recreating the data source.

Given this limitation, the following questions remain open:

• Will StackBlitz introduce built‑in migration or rollback tooling for databases in future releases?
• What is the recommended workflow for managing schema changes when using external databases within a StackBlitz project?
• Can existing migration frameworks (e.g., Knex, TypeORM) be seamlessly integrated into a StackBlitz environment?