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

@initfinity/plugin-smoke-test

v0.1.0

Published

End-to-end smoke test that exercises the full Initfinity plugin API

Readme

@initfinity/plugin-smoke-test

End-to-end smoke test that exercises the full Initfinity plugin API.

Load and activate this plugin to confirm that every surface of the plugin system is wired up and working. It is generated from the plugin Turbo generator and serves as both a correctness check and a reference implementation.

What it exercises

| API surface | Detail | |---|---| | commands.register | Registers a smoke-test terminal command that prints the event log | | hooks.beforeFlowExecute | SyncHook — logs node count | | hooks.afterFlowExecute | AsyncSeriesHook — logs execution status | | hooks.beforeNodeExecute | SyncWaterfallHook — passes context through unchanged | | hooks.afterNodeExecute | AsyncSeriesHook — logs node id | | hooks.onFlowValidate | SyncBailHook — fails empty flows | | hooks.modifyNodeDefinitions | SyncWaterfallHook — passes definitions through unchanged | | hooks.onSettingsChange | SyncHook — logs changed setting keys | | hooks.onThemeChange | SyncHook — logs theme/mode | | engine.subscribe | Logs every execution-state change | | engine.registerNodeType | Registers a custom smoke-test:ping compute node | | engine.removeNodeType | Removes smoke-test:ping on dispose | | events.emit / events.on | Ping → pong round-trip via the event bus | | settings.get | Reads and logs current settings keys | | settings.subscribe | Receives future settings change callbacks | | ui.addStatusBarItem | "Smoke Test" button in bottom status bar | | ui.addNavbarItem | 🦎 icon in left sidebar | | ui.addInspectorTab | "Smoke Test" tab in right inspector panel | | ui.addContextMenuItem (node) | "Smoke Test (node)" in node context menu | | ui.addContextMenuItem (edge) | "Smoke Test (edge)" in edge context menu |

Visible UI elements

When activated, you will see visible, clickable components in these locations:

  • Status Bar: "Smoke Test" button at bottom
  • Navbar: 🦎 icon in left sidebar
  • Inspector: "Smoke Test" tab with active event log display (right panel)
  • Context Menus: Red "Smoke Test (target)" items in node/edge right-click menus

All buttons log their activation to the plugin's event log. Click any button to see it appear in the browser console and Inspector tab.

Usage

import { loadPluginFromVFS } from '../src/plugins/plugin-loader';

const mod = await loadPluginFromVFS(fs, 'plugin-smoke-test');
manager.install(mod);
await manager.activate('plugin-smoke-test');

// Run the registered terminal command to dump the event log:
//   smoke-test

Or load from the built dist file:

import { loadPluginFromURL } from '../src/plugins/plugin-loader';

const mod = await loadPluginFromURL('/plugins/plugin-smoke-test/dist/index.js');
manager.install(mod);
await manager.activate('plugin-smoke-test');

Observing results

After activation, open the browser console. You should see lines like:

[smoke-test] register() — smoke test starting
[smoke-test] commands.register ✓
[smoke-test] hooks.tap ✓ (all 8 hooks)
[smoke-test] engine.subscribe ✓
[smoke-test] events:ping received — echoing pong
[smoke-test] events:pong received — {...}
[smoke-test] events.emit/on ✓
[smoke-test] settings.get ✓ — keys:[...]
[smoke-test] settings.subscribe ✓
[smoke-test] ui.addStatusBarItem ✓
[smoke-test] ui.addNavbarItem ✓
[smoke-test] ui.addInspectorTab ✓ (icon + panel)
[smoke-test] ui.addContextMenuItem ✓ (node)
[smoke-test] ui.addContextMenuItem ✓ (edge)
[smoke-test] register() complete — all API surfaces exercised ✓
[smoke-test] engine.registerNodeType ✓ (smoke-test:ping)

Test the components

  1. Click any visible button/icon → look for the button-click log entries
  2. Open the Inspector → click the "Smoke Test" tab to see the last 5 logged events
  3. Right-click canvas/nodes/edges → see the injected red "Smoke Test (target)" menu items
  4. Open terminal and run smoke-test → dumps the full event log to console

Run smoke-test in the terminal to reprint the full ordered event log at any time.

Development

# Type-check
pnpm check-types

# Run tests
pnpm test

# Build (outputs dist/index.js for dynamic import)
pnpm build

License

MIT