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

@lokomotif/blueprint-n8n

v0.1.0

Published

Adapt Lokomotif RTCSG flows to n8n workflow JSON.

Readme

@lokomotif/blueprint-n8n

Adapt a ComposedPrompt to an n8n workflow JSON that imports cleanly via Workflows → Import from File.

Install

pnpm add @lokomotif/sdk @lokomotif/blueprint-n8n

Usage

import { compose, loadModules } from '@lokomotif/sdk';
import { adaptToN8n, renderN8nJson } from '@lokomotif/blueprint-n8n';
import { writeFileSync } from 'node:fs';

const modules = loadModules([...], { modulesDir });
const composed = compose(modules);
const workflow = adaptToN8n(composed, {
  workflowName: 'aml-review',
});

writeFileSync('aml-review.n8n.json', renderN8nJson(workflow));

API

adaptToN8n(composed, options)  → N8nWorkflow
renderN8nJson(workflow)         → string  (importable JSON)

What goes where

The output workflow has three nodes:

  1. Manual Triggern8n-nodes-base.manualTrigger. The starting node; in production replace with your real trigger (webhook, schedule, etc.).
  2. Anthropic Chat@n8n/n8n-nodes-langchain.lmChatAnthropic carrying the composed RTCSG prompt as the system message and the trigger payload as the user message.
  3. Set outputn8n-nodes-base.set exposing the LLM response to downstream nodes.

The composition hash is recorded in the workflow's meta field so an n8n export can be traced back to the originating Lokomotif composition.

Caveats

n8n's node parameter shape evolves between releases. The output here targets the LangChain integration nodes that ship with current n8n. Operators may need to swap the LLM node type for their preferred provider.

Phase status

Ships in Phase 7 of IMPLEMENTATION_PLAN.md.