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

@revenexx/studio-integrations

v0.5.1

Published

Integration Studio (core: workflows, node editor, runs, schedules, credentials, secrets, audit) as a standalone, publishable Nuxt module.

Readme

@revenexx/studio-integrations

The revenexx Integration Studio (core: Dashboard, Workflows + node editor, Runs, Schedules, Credentials, Secrets, Audit) as a distributable Nuxt module. Registers its /integrations/* pages, components and composables. Data/auth flow through the usePlatformAuth / usePlatformTenant seam (from @revenexx/studio-shared).

Install

Public on npm — no registry config or token needed:

pnpm add @revenexx/studio-integrations @revenexx/studio-shared @revenexx/studio

Use

// nuxt.config.ts
export default defineNuxtConfig({
  // studio-shared is a Nuxt MODULE since 0.2.0 (shell primitives by their
  // bare names + the platform provider) — do NOT `extends` it anymore.
  modules: ['@solar-icons/nuxt', '@revenexx/studio-shared', '@revenexx/studio-integrations'],
})

Point it at your Integrations backend via NUXT_PUBLIC_INTEGRATIONS_API and supply a token/tenant through the platform provider (override usePlatformAuth / usePlatformTenant, or the standalone defaults read NUXT_PUBLIC_DEV_TOKEN / NUXT_PUBLIC_DEV_TENANT).

⚠️ Tailwind: you MUST scan this package

The module ships its runtime as source-ish .vue; Tailwind generates the classes from your build. Scan both this module and studio-shared, or component styling silently breaks:

@import "tailwindcss";
@import "@revenexx/studio/tokens";
@import "@revenexx/studio/fonts";
@source "../node_modules/@revenexx/studio-shared/dist/runtime";
@source "../node_modules/@revenexx/studio-integrations/dist/runtime";

Adjust the relative paths to reach node_modules from your CSS file.

Peers

@revenexx/studio, @revenexx/studio-shared ^0.2 (module form), nuxt ^4, vue ^3.5, @vue-flow/* + @dagrejs/dagre (workflow editor), lucide-vue-next; register @solar-icons/nuxt in the host.

Develop

This repo is the source of truth for the module (it used to live in the cockpit monorepo under packages/studio-integrations).

pnpm install     # runs the module `prepare` (nuxt-module-build)
pnpm test        # vitest
pnpm build       # dist/

Hosts to develop against:

  • Playground (playground/, in this repo): thin standalone Nuxt host that loads the module from src/ — see playground/README.md for the full runbook against a local integrations service (docker compose -f playground/docker-compose.dev.yml up).
  • Cockpit (../revenexx-cockpit): its dev server loads this module from the sibling checkout's src/module.ts automatically (dev-from-source, see the cockpit's nuxt.config.ts). Edit src/** here, the cockpit HMRs.
  • Integrations service (../integrations): the studio-ui dev host consumes a packed tarball — studio-ui/scripts/pack-vendor.sh builds and packs this repo into studio-ui/vendor/.

Release

Bump version in package.json and push to main — CI (.github/workflows/publish.yml) publishes any version that isn't on npm yet, via npm Trusted Publishing (the trusted publisher on npmjs is bound to this repo + workflow file).