plugin-full-frontend-system-migration

Migrate Backstage plugins from legacy to new frontend systems.

34.1k|7.5k|Updated Jan 24, 2020
One-click install
npx skills add https://github.com/backstage/backstage --skill plugin-full-frontend-system-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-full-frontend-system-migration
Source: https://github.com/backstage/backstage/tree/main/docs/.well-known/skills/plugin-full-frontend-system-migration
Command: npx skills add https://github.com/backstage/backstage --skill plugin-full-frontend-system-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams through fully migrating Backstage plugins from the legacy frontend system to the new frontend system, removing backward compatibility entirely and consolidating modernization efforts.

Core Features & Use Cases

  • End-to-end migration: replace old plugin definitions and routing with the new frontend-plugin-api equivalents, removing all reliance on the old core-plugin-api.
  • API refactor and ownership: adopt ApiBlueprints with explicit plugin ownership to enforce API boundaries across the app.
  • Routing and UI modernization: convert internal routing to PageBlueprint/SubPageBlueprint patterns and migrate pages to the framework-driven UI.

Quick Start

Begin the migration by replacing old API and routing usage to the frontend-plugin-api based definitions.

Frequently Asked Questions about plugin-full-frontend-system-migration

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

FAQPage Schema
How do I migrate Backstage plugins to the new frontend system?

To migrate Backstage plugins to the new frontend system, replace old core-plugin-api definitions with frontend-plugin-api equivalents like createFrontendPlugin, ApiBlueprint, and PageBlueprint, following a checklist to update imports, remove legacy code, and modernize UI components.

What is the difference between core-plugin-api and frontend-plugin-api in Backstage?

The core-plugin-api is the legacy system requiring backward compatibility, whereas the frontend-plugin-api enforces API boundaries through explicit plugin ownership using ApiBlueprints and modernizes routing with PageBlueprint and SubPageBlueprint patterns.

Can I use PageBlueprint and SubPageBlueprint to replace internal routing in Backstage plugins?

Yes, you can convert internal routing in Backstage plugins by replacing legacy routing mechanisms with PageBlueprint and SubPageBlueprint patterns to adopt a framework-driven, UI-centric approach.

Does migrating Backstage plugins to frontend-plugin-api remove backward compatibility?

Yes, fully migrating Backstage plugins to the frontend-plugin-api removes backward compatibility entirely, eliminating dependence on the old core plugin API and consolidating modernization efforts across internal and published plugins.

How do I update API factories when modernizing Backstage plugin routing?

Update API factories by adopting ApiBlueprints with explicit plugin ownership to enforce API boundaries across the app, replacing old API factory definitions with frontend-plugin-api equivalents during the migration checklist process.