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

@dkolosovsky/reactor-client

v0.1.0

Published

Thin HTTP SDK for the Reactor service. Browser- and Node-friendly. POSTs Idea triplets, reconstructs typed TextToolsError instances from server responses, re-exports text-tools builders.

Readme

@reactor/client

Thin HTTP SDK for @reactor/service. Consumers (Chrome extension, hh.ru CLI scripts, future apps) build Idea triplets locally and dispatch them to a running Reactor service via this client. Browser-friendly (Chrome MV3) and Node-friendly (CLI).

Status

v0.1.0 - reactor client genesis (sub-project 4.0).

Usage

import { ReactorClient, buildCoverLetterIdea } from '@reactor/client';

const client = new ReactorClient({ baseUrl: 'http://localhost:3030' });

const idea = buildCoverLetterIdea({
  vacancy: { title: 'Senior FE', description: 'React, 5+ years' },
  resume: { title: 'FE Eng', content: '7 years React, TypeScript' },
});

const solution = await client.execute(idea, {
  providerConfig: {
    provider: 'openrouter',
    model: 'openai/gpt-4o-mini',
    apiKey: process.env.OPENROUTER_API_KEY ?? '',
  },
});

console.log(solution.output);

The same pattern works for buildScoreIdea (returns { score, reasoning, skillMatch }) and buildQuestionsIdea (returns { qaPairs }).

Error handling

Activity errors come through as typed TextToolsError subclasses (LLMQuotaError, LLMTimeoutError, IdeaSchemaError, etc.) reconstructed from the service response. HTTP-level issues (network failure, malformed response, unknown error class) throw ReactorClientError.

import { LLMQuotaError, ReactorClientError } from '@reactor/client';

try {
  const sol = await client.execute(idea, { providerConfig });
} catch (err) {
  if (err instanceof LLMQuotaError) {
    console.log(`retry after ${err.retryAfterMs}ms`);
  } else if (err instanceof ReactorClientError) {
    console.log('service unreachable or malformed:', err.message);
  } else {
    throw err;
  }
}

Cancellation

ReactorClient.execute(idea, { providerConfig, signal }) forwards the AbortSignal to the underlying fetch, so consumers can wire it to their own AbortController for timeout / abort flows.

Dependencies

  • Runtime: @reactor/text-tools (for builder re-exports and the typed error hierarchy).
  • Type-only: @kolosochek/reactor-core (for Idea / Solution shapes); zero runtime cost on the consumer side.

Spec / plan

  • Spec: docs/specs/2026-04-26-reactor-service-design.md
  • Plan: docs/plans/2026-04-26-reactor-service-genesis.md