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

@palinc/nirnam

v1.4.1

Published

A three-layer hybrid message bus for micro-frontend communication using SharedWorker and BroadcastChannel

Readme

@palinc/nirnam

A three-layer hybrid message bus for micro-frontend communication and browser-native AI agents — built on SharedWorker and BroadcastChannel with zero runtime dependencies.

Install

npm install @palinc/nirnam

Quick start

import { createBus } from '@palinc/nirnam';

const bus = createBus();

// Subscribe
bus.subscribe<string>('greet', msg => console.log(msg));

// Publish
bus.publish('greet', 'Hello from another MFE!');

That's it. No server, no config, no boilerplate. Works across iframes, Module Federation remotes, and independently-loaded scripts on the same page.


Core message patterns

Pub / Sub

Fire-and-forget broadcast. Any number of subscribers receive every message.

const unsub = bus.subscribe<{ user: string }>('user:login', ({ user }) => {
  console.log('logged in:', user);
});

bus.publish('user:login', { user: 'alice' });

unsub(); // stop listening

Request / Reply

One sender, one handler, typed generics, built-in timeout.

// In the service MFE
bus.handle<{ id: number }, { name: string }>('product:get', async ({ id }) => {
  return { name: await db.getProductName(id) };
});

// In the consumer MFE
const product = await bus.request<{ id: number }, { name: string }>(
  'product:get',
  { id: 42 }
);

Streaming

Push a sequence of values from handler to consumer — perfect for LLM token streams or progress updates.

// Handler
bus.handleStream<{ prompt: string }, string>('llm:stream', async function* ({ prompt }) {
  for await (const token of llm.stream(prompt)) {
    yield token;
  }
});

// Consumer
for await (const token of bus.requestStream<{ prompt: string }, string>('llm:stream', { prompt: 'Hello' })) {
  process.stdout.write(token);
}

React integration

# no extra install — included in @palinc/nirnam
import { NirnamProvider, useNirnam, useNirnamPublish } from '@palinc/nirnam/react';
import { createBus } from '@palinc/nirnam';

const bus = createBus();

function App() {
  return (
    <NirnamProvider bus={bus}>
      <Counter />
      <Controls />
    </NirnamProvider>
  );
}

function Counter() {
  const count = useNirnam<number>('counter', 0);
  return <div>Count: {count}</div>;
}

function Controls() {
  const publish = useNirnamPublish();
  return <button onClick={() => publish('counter', c => c + 1)}>+1</button>;
}

All React hooks:

| Hook | Returns | |------|---------| | useNirnam<T>(topic, initial?) | Latest value on that topic | | useNirnamPublish() | Stable publish(topic, payload) function | | useNirnamRequest() | Stable request(topic, payload, timeout?) function | | useNirnamRequestStream() | Stable requestStream(topic, payload) function | | useNirnamBus() | Raw NirnamBus instance |


Angular integration

import { provideNirnam, NirnamService } from '@palinc/nirnam/angular';

// main.ts (standalone)
bootstrapApplication(AppComponent, {
  providers: [provideNirnam()]
});

// or NgModule
@NgModule({
  imports: [NirnamModule.forRoot()]
})
@Component({ ... })
export class MyComponent {
  private nirnam = inject(NirnamService);

  count$ = this.nirnam.subscribe<number>('counter');

  increment() {
    this.nirnam.publish('counter', 42);
  }
}

Agent framework

Build LLM-powered agents that run entirely in the browser — no backend required.

import { createAgent } from '@palinc/nirnam/agents';

const agent = createAgent({
  agentId: 'assistant',
  llm: {
    url: 'http://localhost:11434/api/chat', // Ollama
    model: 'llama3.2',
  },
  systemPrompt: 'You are a helpful assistant.',
  bus,
});

await agent.ready;

// Back-and-forth conversation (history accumulates)
const reply = await agent.chat('What is the capital of France?');

// One-shot task (history is not modified)
const summary = await agent.run('Summarise this text: ...');

// Single LLM call, no tool loop
const label = await agent.process('Classify: positive or negative? "Great product!"');

// Streaming
for await (const token of agent.chatStream('Tell me a story')) {
  process.stdout.write(token);
}

LLM auto-detection — no provider flag needed. The URL decides:

| URL pattern | Provider | |-------------|----------| | localhost:11434 | Ollama | | *.anthropic.com or claude-* model | Anthropic | | Anything else with /v1/chat/completions | OpenAI-compatible |

Built-in tools

import { presets } from '@palinc/nirnam/agents';

const agent = createAgent({
  agentId: 'coder',
  llm: { url: '...', model: '...' },
  ...presets.filesystem(), // adds readFile / listDirectory / writeFile tools
  bus,
});

// User picks a folder — agent can read/write it
await agent.requestFolderAccess();

Available presets: filesystem(), codeReview(), summarizer(), monitor().

React hooks for agents

import { useAgent, useAgentChat } from '@palinc/nirnam/agents/react';

function Chat() {
  const agent = useAgent({ agentId: 'assistant', llm: { url: '...', model: '...' }, bus });
  const { messages, send, isStreaming } = useAgentChat(agent);

  return (
    <>
      {messages.map(m => <div key={m.id}>[{m.role}] {m.content}</div>)}
      <button onClick={() => send('Hello!')} disabled={isStreaming}>Send</button>
    </>
  );
}

Multi-agent topologies

import { createAgent, connectAgents } from '@palinc/nirnam/agents';

const extractor = createAgent({ agentId: 'extractor', llm, bus });
const summariser = createAgent({ agentId: 'summariser', llm, bus });

// Output of extractor becomes input of summariser
connectAgents([extractor, summariser], {
  topology: 'pipeline',
  topic: 'pipeline:data',
});

Testing agents

import { mockLLM } from '@palinc/nirnam/agents/testing';

const agent = createAgent({
  agentId: 'test-agent',
  llm: mockLLM(['First reply', 'Second reply']),
  bus,
});

MCP Transport

Wire any MCP-compatible server or client over the Nirnam bus. No HTTP, no WebSocket — message routing is handled by the SharedWorker.

import { NirnamMCPTransport } from '@palinc/nirnam/mcp';
import { Client } from '@modelcontextprotocol/sdk/client/index.js';

// Install peer dep: npm install @modelcontextprotocol/sdk

const transport = new NirnamMCPTransport({
  agentId: 'mcp-client',
  targetAgentId: 'mcp-server',
  bus,
});

const client = new Client({ name: 'my-client', version: '1.0.0' }, { capabilities: {} });
await client.connect(transport);

const result = await client.callTool({ name: 'my_tool', arguments: {} });

Cross-tab communication

By default the bus connects every script on the same page via a Blob-URL SharedWorker. To route messages across tabs you need a static worker URL — add one of the build plugins.

Vite

// vite.config.ts
import { nirnamPlugin } from '@palinc/nirnam/vite';

export default {
  plugins: [nirnamPlugin()]
};

Rsbuild

// rsbuild.config.ts
import { nirnamPlugin } from '@palinc/nirnam/rsbuild';

export default defineConfig({
  plugins: [nirnamPlugin()]
});

Webpack

// webpack.config.js
const { NirnamWebpackPlugin } = require('@palinc/nirnam/webpack');

module.exports = {
  plugins: [new NirnamWebpackPlugin()]
};

Each plugin copies the SharedWorker script into your public directory and injects __NIRNAM_STATIC_WORKER_URL__ at build time. createBus() picks it up automatically — no code changes needed.

Cross-tab agents

Run one LLM agent in a host tab and let any other tab proxy into it over the static worker:

// host tab
import { createAgent } from '@palinc/nirnam/agents';

const agent = createAgent({
  agentId: 'assistant',
  scope: 'page',   // registers in the shared worker registry
  llm: { url: '...', model: '...' },
  bus,
});
// any other tab
import { createAgentProxy } from '@palinc/nirnam/agents';

const proxy = createAgentProxy('assistant', bus);

const reply = await proxy.chat('Hello!'); // routed to the host tab

Message persistence

Replay messages to late-joining subscribers using IndexedDB.

// Publisher
bus.publish('notifications', { text: 'Server restarted' }, { persist: true, ttl: 60_000 });

// Subscriber (gets last 10 messages immediately on subscribe)
bus.subscribe('notifications', handler, { replay: 10 });

TypeScript

The package ships .d.ts declaration files for every subpath export. No @types package required.

import type { NirnamBus, NirnamBusOptions, AgentConfig, AgentStatus } from '@palinc/nirnam';
import type { NirnamMCPTransport } from '@palinc/nirnam/mcp';

Browser support

Requires SharedWorker and BroadcastChannel support (all modern browsers; no IE11). The agent framework additionally uses fetch for LLM calls and optionally the File System Access API for folder tools.


Subpath exports

| Import | Contents | |--------|----------| | @palinc/nirnam | createBus, NirnamBus, DataEvent | | @palinc/nirnam/react | NirnamProvider, useNirnam, useNirnamPublish, … | | @palinc/nirnam/angular | NirnamService, provideNirnam, NirnamModule | | @palinc/nirnam/agents | createAgent, createAgentProxy, connectAgents, presets | | @palinc/nirnam/agents/react | useAgent, useAgentChat, useAgentStatus | | @palinc/nirnam/agents/testing | mockLLM | | @palinc/nirnam/mcp | NirnamMCPTransport | | @palinc/nirnam/vite | nirnamPlugin | | @palinc/nirnam/rsbuild | nirnamPlugin | | @palinc/nirnam/webpack | NirnamWebpackPlugin |