Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: structure-of-a-plugin.md

id: structure-of-a-plugin title: Structure of a Plugin description: Details about structure of a plugin Nice, you have a new plugin! We'll soon see how we can develop it into doing great things. But first off, let's look at what we get out of the box. The new plugin should look something like: ``` new-plugin/ dev/ index.ts node_modules/ src/ components/ ExampleComponent/ ExampleComponent.test.tsx ExampleComponent.tsx index.ts ExampleFetchComponent/ ExampleFetchComponent.test.tsx ExampleFetchComponent.tsx index.ts index.ts plugin.test.ts plugin.ts routes.ts setupTests.ts .eslintrc.js package.json README.md ``` You might note a thing or two. Yes, a plugin looks like a mini project on it's own with a `package.json` and a `src` folder. And this is because we want plugins to be separate packages. This makes it possible to ship plugins on npm and it lets you work on a plugin in isolation, without loading all the other plugins in a potentially big Backstage app. The `index.ts` files are there to let us import from the folder path and not specific files. It's a way to have control over the exports in one file per folder. You get a readme to populate with info about your plugin and a package.json to declare the plugin dependencies, metadata and scripts. In the `src` folder we get to the interesting bits. Check out the `plugin.ts`: ```jsx import { createPlugin, createRoutableExtension, } from '@backstage/core-plugin-api'; import { rootRouteRef } from './routes'; export const examplePlugin = createPlugin({ id: 'example', routes: { root: rootRouteRef, }, }); export const ExamplePage = examplePlugin.provide( createRoutableExtension({ name: 'ExamplePage', component: () => import('./components/ExampleComponent').then(m => m.ExampleComponent), mountPoint: rootRouteRef, }), ); ``` This is where the plugin is created and where it creates and exports extensions that can be imported and used the app. See reference docs for or introduction to the new . The generated plugin includes two example components to showcase how we structure our plugins. There are usually one or multiple page components and next to them you can split up the UI in as many components as you feel like. We have the `ExampleComponent` to show an example Backstage page component. The `ExampleFetchComponent` showcases the common task of making an async request to a public API and plot the response data in a table using Material UI components. You may tweak these components, rename them and/or replace them completely. There are two things needed for a Backstage app to start making use of a plugin. Add plugin as dependency in `app/package.json` Import and use one or more plugin extensions, for example in `app/src/App.tsx`. Luckily both of these steps happen automatically when you create a plugin with the Backstage CLI. If your plugin needs to communicate with services outside the Backstage environment you will probably face challenges like CORS policies and/or backend-side authorization. To smooth this process out you can use proxy - either the one you already have (like Nginx, HAProxy, etc.) or the proxy-backend plugin that we provide for the Backstage backend.