paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 1 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
docs/frontend-system/building-apps/01-index.md
+3 -3
View File
@@ -18,12 +18,12 @@ The create-app CLI requires Node.js Active LTS Release, see the [prerequisites d
:::
```sh
# The command bellow creates a Backstage App inside the current folder.
# The command below creates a Backstage App inside the current folder.
# The name of the app-folder is the name that was provided when prompted.
npx @backstage/create-app@latest --next
npx @backstage/create-app@latest
```
Using the `--next` flag will result in a Backstage app using the New Frontend System which will be further explained in the sections below.
This will create a Backstage app using the new frontend system which will be further explained in the sections below.
## The app instance
docs/frontend-system/building-apps/08-migrating.md
+1 -33
View File
@@ -899,39 +899,7 @@ It's encouraged that once you switch over to using the new frontend system, that
This practice is also pretty important early on, as it's going to help you get familiar with the practices of the new frontend system.
When creating a new Backstage app with `create-app` and using the `--next` flag you'll automatically get these choices in the `yarn new` command, but if you want to bring these templates to an older app, you can add the following to your root `package.json`:
```json
{
...
"scripts": {
...
"new": "backstage-cli new"
},
"backstage": {
"cli": {
"new": {
"globals": {
"license": "UNLICENSED"
},
"templates": [
"@backstage/cli-module-new/templates/new-frontend-plugin",
"@backstage/cli-module-new/templates/new-frontend-plugin-module",
"@backstage/cli-module-new/templates/backend-plugin",
"@backstage/cli-module-new/templates/backend-plugin-module",
"@backstage/cli-module-new/templates/plugin-web-library",
"@backstage/cli-module-new/templates/plugin-node-library",
"@backstage/cli-module-new/templates/plugin-common-library",
"@backstage/cli-module-new/templates/web-library",
"@backstage/cli-module-new/templates/node-library",
"@backstage/cli-module-new/templates/catalog-provider-module",
"@backstage/cli-module-new/templates/scaffolder-backend-module"
]
}
}
}
}
```
The `yarn new` command now defaults to the new frontend system templates for frontend plugins. If you have an older app that was created before this change, you can simply update the `@backstage/cli-module-new` package to get access to the new templates.
## Troubleshooting