Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@backstage/frontend-defaults

backstage344.3kApache-2.00.3.2TypeScript support: included

null

readme

headline

Backstage

English | 한국어 | 中文版 | Français

License CNCF Status Discord Code style Codecov OpenSSF Best Practices OpenSSF Scorecard

What is Backstage?

Backstage is an open source framework for building developer portals. Powered by a centralized software catalog, Backstage restores order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly without compromising autonomy.

Backstage unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.

software-catalog

Out of the box, Backstage includes:

  • Backstage Software Catalog for managing all your software such as microservices, libraries, data pipelines, websites, and ML models
  • Backstage Software Templates for quickly spinning up new projects and standardizing your tooling with your organization’s best practices
  • Backstage TechDocs for making it easy to create, maintain, find, and use technical documentation, using a "docs like code" approach
  • Plus, a growing ecosystem of open source plugins that further expand Backstage’s customizability and functionality

Backstage was created by Spotify but is now hosted by the Cloud Native Computing Foundation (CNCF) as an Incubation level project. For more information, see the announcement.

Project roadmap

For information about the detailed project roadmap including delivered milestones, see the Roadmap.

Getting Started

To start using Backstage, see the Getting Started documentation.

Documentation

The documentation of Backstage includes:

Community

To engage with our community, you can use the following resources:

Governance

See the GOVERNANCE.md document in the backstage/community repository.

License

Copyright 2020-2025 © The Backstage Authors. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: https://www.linuxfoundation.org/trademark-usage

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0

Security

Please report sensitive security issues using Spotify's bug-bounty program rather than GitHub.

For further details, see our complete security release process.

changelog

@backstage/frontend-defaults

0.3.2

Patch Changes

0.3.2-next.1

Patch Changes

0.3.2-next.0

Patch Changes

0.3.1

Patch Changes

0.3.1-next.0

Patch Changes

0.3.0

Minor Changes

  • 76832a9: BREAKING: Removed the deprecated CreateAppFeatureLoader and support for it in other APIs. Switch existing usage to use the newer createFrontendFeatureLoader from @backstage/frontend-plugin-api instead.

  • 5e12252: BREAKING: Restructured some of option fields of createApp and createSpecializedApp.

    • For createApp, all option fields except features and bindRoutes have been moved into a new advanced object field.
    • For createSpecializedApp, all option fields except features, config, and bindRoutes have been moved into a new advanced object field.

    This helps highlight that some options are meant to rarely be needed or used, and simplifies the usage of those options that are almost always required.

    As an example, if you used to supply a custom config loader, you would update your code as follows:

     createApp({
   features: [...],
-  configLoader: new MyCustomLoader(),
+  advanced: {
+    configLoader: new MyCustomLoader(),
+  },
 })

Patch Changes

  • 22de964: Deprecated createPublicSignInApp, which has been replaced by the new appModulePublicSignIn from @backstage/plugin-app/alpha instead.
  • e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.
  • 8b1bf6e: Deprecated new frontend system config setting app.experimental.packages to just app.packages. The old config will continue working for the time being, but may be removed in a future release.
  • 7adc846: Added support for passing through allowUnknownExtensionConfig as a flag
  • e5a0a99: BREAKING: The loadingComponent option has been renamed to loadingElement, which is now found under advanced.loadingElement. The default loading element has also been switched to <Progress /> from @backstage/core-components. This is of course an improvement over the previous "Loading..." text, but also helps prevent flicker when the app loading is fast.
  • Updated dependencies

0.3.0-next.3

Minor Changes

  • 5e12252: BREAKING: Restructured some of option fields of createApp and createSpecializedApp.

    • For createApp, all option fields except features and bindRoutes have been moved into a new advanced object field.
    • For createSpecializedApp, all option fields except features, config, and bindRoutes have been moved into a new advanced object field.

    This helps highlight that some options are meant to rarely be needed or used, and simplifies the usage of those options that are almost always required.

    As an example, if you used to supply a custom config loader, you would update your code as follows:

     createApp({
   features: [...],
-  configLoader: new MyCustomLoader(),
+  advanced: {
+    configLoader: new MyCustomLoader(),
+  },
 })

Patch Changes

0.3.0-next.2

Minor Changes

  • 76832a9: BREAKING: Removed the deprecated CreateAppFeatureLoader and support for it in other APIs. Switch existing usage to use the newer createFrontendFeatureLoader from @backstage/frontend-plugin-api instead.

Patch Changes

0.2.5-next.1

Patch Changes

0.2.5-next.0

Patch Changes

0.2.4

Patch Changes

0.2.4-next.1

Patch Changes

0.2.4-next.0

Patch Changes

0.2.3

Patch Changes

0.2.3-next.1

Patch Changes

0.2.3-next.0

Patch Changes

0.2.2

Patch Changes

0.2.2-next.3

Patch Changes

0.2.2-next.2

Patch Changes

0.2.2-next.1

Patch Changes

0.2.2-next.0

Patch Changes

0.2.1

Patch Changes

0.2.1-next.1

Patch Changes

0.2.1-next.0

Patch Changes

0.2.0

Minor Changes

  • 4823831: Introduced a createFrontendFeatureLoader() function, as well as a FrontendFeatureLoader interface, to gather several frontend plugins, modules or feature loaders in a single exported entrypoint and load them, possibly asynchronously. This new feature, very similar to the createBackendFeatureLoader() already available on the backend, supersedes the previous CreateAppFeatureLoader type which has been deprecated.
  • 8250ffe: BREAKING: Dropped support for the removed opaque @backstage/ExtensionOverrides and @backstage/BackstagePlugin types.

Patch Changes

0.2.0-next.2

Minor Changes

  • 8250ffe: BREAKING: Dropped support for the removed opaque @backstage/ExtensionOverrides and @backstage/BackstagePlugin types.

Patch Changes

0.1.7-next.1

Patch Changes

0.1.7-next.0

Patch Changes

0.1.6

Patch Changes

0.1.6-next.3

Patch Changes

0.1.6-next.2

Patch Changes

0.1.6-next.1

Patch Changes

0.1.6-next.0

Patch Changes

0.1.5

Patch Changes

0.1.5-next.0

Patch Changes

0.1.4

Patch Changes

0.1.4-next.2

Patch Changes

0.1.4-next.1

Patch Changes

0.1.4-next.0

Patch Changes

0.1.2

Patch Changes

0.1.2-next.2

Patch Changes

0.1.2-next.1

Patch Changes

0.1.2-next.0

Patch Changes

0.1.1

Patch Changes

0.1.1-next.2

Patch Changes

0.1.1-next.1

Patch Changes

0.1.1-next.0

Patch Changes

0.1.0

Minor Changes

  • 7c80650: Initial release of this package, which provides a default app setup through the createApp function. This replaces the existing createApp method from @backstage/frontend-app-api.

Patch Changes

0.1.0-next.1

Patch Changes

0.1.0-next.0

Minor Changes

  • 7c80650: Initial release of this package, which provides a default app setup through the createApp function. This replaces the existing createApp method from @backstage/frontend-app-api.

Patch Changes