npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@codeowners/backstage-plugin

v0.2.1

Published

Welcome to the codeowners plugin!

Downloads

10

Readme

CODEOWNERS.com Backstage Plugin

Welcome to the codeowners plugin!

Backstage Configuration

You'll need to configure a proxy to CODEOWNERS.com and place the CODEOWNERS.com cards in your catalog entity pages.

Create a CODEOWNERS.com Personal Access Token

  1. Login to your CODEOWNERS.com account
  2. Create a Personal Access Token (PAT)
  3. Set your PAT as an environment variable, CODEOWNERS_API_KEY in the environment where you run Backstage.

Configure API Proxy

Configure Backstage so that the Codeowners plugin can communicate to the codeowners.com API:

# in app-config.yaml
proxy:
  '/codeowners/api':
    target: https://api.codeowners.com/api/v1
    headers:
      Authorization: Bearer ${CODEOWNERS_API_KEY}

Reminder: Be sure to create CODEOWNERS_API_KEY environment variable where you run your Backstage server.

Add the CODEOWNERS.com Settings Page

  1. Add a route to the Codeowners settings page:
// packages/app/src/App.tsx
import { CodeownersSettingsPage } from "@codeowners/backstage-plugin";

const routes = (
  <FlatRoutes>
    {/* snip... */}
    <Route path="/codeowners" element={<CodeownersSettingsPage />} />
  </FlatRoutes>
);
  1. Create a link in the Backstage sidebar to the Codeowners settings page
// packages/app/src/components/Root/Root.tsx
import { CodeownersIcon } from "@codeowners/backstage-plugin";

export const Root = ({ children }: PropsWithChildren<{}>) => (
  <SidebarPage>
    <Sidebar>
      {/* snip...  */}
      <SidebarItem icon={CodeownersIcon} to="codeowners" text="CODEOWNERS.com" />
    </Sidebar>
  </SidebarPage>
);

Add the CODEOWNERS.com Backstage Plugin Cards

Add the CODEOWNERS.com module to your Backstage instance:

yarn add --cwd packages/app @codeowners/backstage-plugin

Import the cards you want to use in the Backstage entity overview page:

 // packages/app/src/components/catalog/EntityPage.tsx

 // Add the following in the imports
 import { ServiceCodeownersCard, RecentChangesCard } from "@codeowners/backstage-plugin";

In the same file, look for the overviewContent object and add the cards you want to use in its Grid:

const overviewContent = (
  <Grid container spacing={3} alignItems="stretch">
    {entityWarningContent}
    { /*  snip other cards... */ }
    <Grid item xs={4}>
      <ServiceCodeownersCard />
    </Grid>
    <Grid item xs={8}>
      <RecentChangesCard />
    </Grid>
  </Grid>
);