paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 42 Packages Projects Releases Wiki Activity

Merge pull request #32700 from backstage/rugvip/new-frontend-system-default

Browse Source 
Make the new frontend system the default for new apps
This commit is contained in:
Patrik Oldsberg
2026-03-17 21:24:11 +01:00
committed by GitHub
parent df15d409a4 65df955244
commit 60e3dcb098
55 changed files with 333 additions and 170 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/cli-new-frontend-templates-default.md
+16
View File
@@ -0,0 +1,16 @@
---
'@backstage/cli': minor
---
**BREAKING**: The CLI templates for frontend plugins have been renamed:
- `new-frontend-plugin` → `frontend-plugin`
- `new-frontend-plugin-module` → `frontend-plugin-module`
- `frontend-plugin` (legacy) → `legacy-frontend-plugin`
To smooth out this breaking change, the CLI now auto-detects which frontend system your app uses based on the dependencies in `packages/app/package.json`. When using the default templates (no explicit `templates` configuration):
- Apps using `@backstage/frontend-defaults` will see the new frontend system templates (`frontend-plugin`, `frontend-plugin-module`)
- Apps using `@backstage/app-defaults` will see the legacy template (displayed as `frontend-plugin`)
This means existing projects that haven't migrated to the new frontend system will continue to create legacy plugins by default, while new projects will get the new frontend system templates. If you have explicit template configuration in your `package.json`, it will be used as-is without any auto-detection.
.changeset/new-frontend-system-default.md
+5
View File
@@ -0,0 +1,5 @@
---
'@backstage/create-app': minor
---
**BREAKING**: The new frontend system is now the default template when creating a new Backstage app. The previous `--next` flag has been replaced with a `--legacy` flag that can be used to create an app using the old frontend system instead.