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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rakesh_gali/plugin-hello-plugin

v0.0.1

Published

A minimal frontend Backstage plugin that displays a `HelloCard` InfoCard.

Downloads

9

Readme

Hello Plugin

A minimal frontend Backstage plugin that displays a HelloCard InfoCard.

How to use:

  • Add the plugin package to your packages/app package.json dependencies or use a workspace reference.
  • Import and register the plugin in your app's plugin registration and routes.

Example import in the app:

import { plugin as helloPlugin } from '@rakesh_gali/plugin-hello-plugin';

If your repository uses Yarn or PNPM workspaces, add a workspace reference from packages/app to the plugin package (or use a direct relative import as in this repository). Then rebuild the app.

Example run (from repo root):

# install deps (yarn or pnpm depending on repo)
yarn install
# build plugin
cd plugins/hello-plugin && yarn build
# start app
cd ../../packages/app && yarn start

Publishing to npm

Before publishing, update package.json fields such as repository.url and version.

If you want to publish to the public npm registry under an organization scope like @backstage, ensure your npm account has permission to publish under that scope. If you don't, choose a different scope (your username or organization) or publish unscoped.

Example publish steps:

# from the plugin folder
cd plugins/hello-plugin

# ensure build artifacts are present
npm run build

# login to npm (if not already)
npm login

# publish (public access)
npm publish --access public

If you plan to publish under @backstage, consult the npm organization owners to add you as a maintainer. Alternatively, change the name field in package.json to @your-scope/plugin-hello-plugin or plugin-hello-plugin.