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

@playrunner/jira

v0.1.3

Published

Jira integration package for Playrunner.

Readme

@playrunner/jira

Jira OAuth, issue actions, and workflow execution for Playrunner.

npm version

View source on GitHub

Install

npm install @playrunner/jira

Add the package as a direct production dependency of the Playrunner frontend, API, and orchestrator. Each build discovers the contribution declared for its surface.

Package surfaces

  • @playrunner/jira exports the Jira integration, configuration panel, and settings UI.
  • @playrunner/jira/api exports OAuth, token refresh, and project API routes.
  • @playrunner/jira/orchestrator exports Jira create and update executors.
  • @playrunner/jira/e2e exports the package-owned E2E contribution.
  • @playrunner/jira/assets/jira.svg exports the package-owned icon.
import jiraIntegration, { JiraSettingsModal } from '@playrunner/jira';
import jiraApiContribution from '@playrunner/jira/api';
import jiraOrchestratorContribution from '@playrunner/jira/orchestrator';

Testing

Run the package checks from the repository root:

npm run format:check --prefix packages/jira
npm run lint --prefix packages/jira
npm run typecheck --prefix packages/jira
npm run test:e2e:mock -- --grep @jira

The E2E scenario validates the Jira OAuth setup form. It runs in deterministic mock mode through the shared Playrunner browser harness, which uses the real frontend, API, authentication, and dedicated E2E database. No Atlassian credentials or live provider requests are required.

Documentation

See the Jira integration documentation for Atlassian OAuth setup, actions, exports, and build integration.

License

Licensed under the Playrunner Sustainable Use License.