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

piilot-pack-pennylane-ui

v0.1.2

Published

Pennylane plugin — frontend contributions (Trésorerie module view, locales) for Piilot core.

Readme

Pennylane plugin — frontend

Frontend contributions of the Pennylane plugin: the Trésorerie module view (including OAuth connection flow, firm client picker and dashboard), plus i18n bundles. Loaded at boot by the core via the plugin UI registry (frontend/src/lib/pluginUI).

Structure

src/
  index.ts                    Entry — calls core.registerModuleView + registerI18nBundle
  TreasuryModuleView.tsx      Root view mounted at /modules/pennylane-treasury
  components/
    ConnectionsList.tsx       Cards + "Add connection" button
    ConnectionCard.tsx        Single connection row (sync status, firm clients, actions)
    ConnectPennylaneDialog.tsx   Plugin-specific OAuth / API-key modal
    FirmClientPicker.tsx      Dropdown to switch between firm clients
    TreasuryDashboard.tsx     Charts + KPIs once a connection is selected
  hooks/
    useConnections.ts         GET/POST/DELETE /plugins/pennylane/connections
    useFirmClients.ts         /plugins/pennylane/firm-clients/*
    useIntegration.ts         OAuth state + token exchange
    useTreasury.ts            /plugins/pennylane/treasury/dashboard
  services/
    pennylaneService.ts       HTTP client for /plugins/pennylane/*
  locales/
    fr.json                   Namespaced under ``pennylane.*``
    en.json
__tests__/
  ...                         Plugin-scoped vitest suite

How the core finds this code

The core's frontend/vite.config.ts declares an alias:

'@plugin/pennylane': path.resolve(__dirname, '../plugins-dev/piilot-pack-pennylane/frontend/src')

At boot the core imports @plugin/pennylane and calls its register(core) default export. Production builds COPY this folder into the frontend Docker image before npm run build.

Imports into the core

All cross-boundary imports go through the @plugin-host/* alias so the migration to runtime module federation (if/when) is a one-liner per import:

import { Button } from '@plugin-host/components/ui/button'
import { apiFetch } from '@plugin-host/services/httpClient'

Direct import ... from '../../../frontend/src/...' is forbidden by the plugin's ESLint rule (to-be-added).

Running tests

npm install
npm run test

Requires the core frontend/ folder at ../../../frontend/ for the @plugin-host alias to resolve.