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

@parodos/plugin-parodos

v0.4.21

Published

Welcome to the parodos plugin!

Downloads

4

Readme

Parodos

Welcome to the parodos plugin!

Setup

  1. Install the plugin into the Backstage app in packages/app
yarn add --cwd packages/app @parodos/plugin-parodos
  1. Add the /parodos/ route in /packages/app/src/App.tsx
import { ParodosPage } from '@parodos/plugin-parodos';

const routes = (
  <FlatRoutes>
    // ...
    <Route path="/parodos" element={<ParodosPage />} />
  </FlatRoutes>
  1. Add Parodos link to the sidebar in packages/app/src/components/Root.tsx

    3.1. Add MeetingRoomIcon import to the top of the file

    import MeetingRoomIcon from '@material-ui/icons/MeetingRoom';

    3.2. Add <SidebarItem icon={MeetingRoomIcon} to="/parodos" text="Parodos" /> after Create... icon. The result will look like this.

    <SidebarItem icon={CreateComponentIcon} to="create" text="Create..." />
    <SidebarItem icon={MeetingRoomIcon} to="/parodos" text="Parodos" />
  2. Add /parodos endpoint to the proxy config in app-config.yaml.

'/parodos':
  target: 'http://localhost:8080/api/v1'
  changeOrigin: true
  redirect: follow
  cache: 'no-cache'
  headers:
    Content-Type: 'application/json'
    accept: 'application/json'

'/parodos-notifications':
  target: 'http://localhost:8081/api/v1'
  changeOrigin: true
  redirect: follow
  cache: 'no-cache'
  headers:
    Content-Type: 'application/json'
    accept: 'application/json'

Local development

For local development, the application username is test, password test.

In addition, the Parodos services need to be running. Please refer up-to-date instructions there, but as a short-cut:

git clone https://github.com/parodos-dev/parodos.git
cd parodos
mvn clean install
cd ./workflow-examples

If the action is failing on an expired token, it can be updated here: https://github.com/organizations/parodos-dev/settings/secrets/actions
./start_workflow_service.sh &
./start_notification_service.sh &

By doing that, there will be two services running at http://localhost:8080 and http://localhost:8081.

Node and package manager versions

While developing the plugin, it is recommended to use volta to ensure the same node and package manager versions are maintained across environments.

Intallation instructions can be found here.

Release

The project is published to the NPM JS Registry on release: https://www.npmjs.com/package/@parodos/plugin-parodos.

To do a release:

  • go to the project release page: https://github.com/parodos-dev/backstage-parodos/releases
  • click Create a new release
  • as a tag, use format vX.Y.Z (mind the v prefix!)
  • as a title, use the same value as for the tag
  • let the release notes to be generated, adjust
  • click Publish release

The on-release GitHub action is triggered, leading to publishing the new version to the NPM registry.

To watch progress: https://github.com/parodos-dev/backstage-parodos/actions/workflows/on-release.yaml

If the action is failing on an expired token, it can be updated here: https://github.com/organizations/parodos-dev/settings/secrets/actions

As a side-effect of the action, a PR bumping the plugin version is created. Do not forget to merge it: https://github.com/parodos-dev/backstage-parodos/pulls