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

@activefs/source-http

v0.1.1

Published

HTTP Source API v1 client and server helpers for ActiveFS remotes.

Readme

@activefs/source-http

Install @activefs/source-http to expose an ActiveFSTree through Source API v1 or consume a Source API as a tree. The package root contains the Node.js client and server helpers; @activefs/source-http/fetch contains the Web-standard server entrypoint for Fetch-compatible runtimes.

The package root requires Node.js 22 or newer.

Install

npm install @activefs/source-http @activefs/core

Run a Node.js source round trip

import { createActiveFS, fsTree, json } from "@activefs/core";
import {
  createHttpSourceClient,
  startActiveFSServer
} from "@activefs/source-http";

let serviceStatus = { ok: true };
const tree = fsTree({
  "/status.json": json(() => serviceStatus)
});

const server = await startActiveFSServer({ tree });

try {
  const remote = createHttpSourceClient({ url: server.url });
  const activefs = createActiveFS().mount("/remote", remote);
  const result = await activefs.read({}, "/remote/status.json");

  console.log(result.content);
} finally {
  await server.close();
}

Output:

{
  "ok": true
}

server.url is the exact discovery URL. Source API clients follow the operation URLs advertised by discovery; they do not infer sibling routes. The standalone Node helper chooses its own default routes, but those paths are not protocol requirements.

Use a Fetch-compatible host

Import the route-independent service from the ./fetch entrypoint:

import { createActiveFSSourceService } from "@activefs/source-http/fetch";

Bind each framework route to the corresponding service operation and advertise the application-owned operation URLs. See the runnable Fetch handler example.

For a hosted source, authenticate the HTTP request and derive the final ActiveFS context in resolveContext. ActiveFS treats this context as opaque: it forwards the values without interpreting them. Request-body auth and metadata are untrusted when that resolver is present. Use a stable, non-secret isolation key for context-sensitive session and cache state; never use a raw credential or a reversible identity value.

Documentation