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

@searchfn/server

v0.1.0

Published

Server SDK for SearchFn - Thin HTTP transport over SearchAdapter

Downloads

84

Readme

@searchfn/server

@searchfn/server exposes SearchFn over the shared @superfunctions/http router abstraction. It does not implement indexing itself; instead, it wraps any SearchAdapter with validated HTTP endpoints.

Installation

npm install @searchfn/server @searchfn/adapter-memory @superfunctions/http

Use a concrete adapter such as @searchfn/adapter-memory, @searchfn/adapter-indexeddb, @searchfn/adapter-postgres, @searchfn/adapter-elasticsearch, or @searchfn/adapter-meilisearch.

Quick Start

import { createSearchFnServer } from "@searchfn/server";
import { MemoryAdapter } from "@searchfn/adapter-memory";

const adapter = new MemoryAdapter();
await adapter.initialize?.({
  resources: [{ name: "docs", searchFields: ["title", "body"] }],
});

const searchfn = await createSearchFnServer({
  adapter,
  basePath: "/searchfn",
});

const response = await searchfn.router.handle(
  new Request("http://localhost/searchfn/search", {
    method: "POST",
    headers: { "content-type": "application/json" },
    body: JSON.stringify({ resource: "docs", query: "hybrid" }),
  }),
);

Endpoints

  • GET /searchfn/status
  • POST /searchfn/index
  • POST /searchfn/search
  • POST /searchfn/search-all
  • POST /searchfn/remove
  • POST /searchfn/clear

All JSON responses use the canonical envelope shape:

{
  "ok": true,
  "result": {}
}

or

{
  "ok": false,
  "error": {
    "code": "DFQL_INVALID",
    "message": "Search query must not be empty"
  }
}

Configuration

type SearchFnServerConfig<TContext> = {
  adapter: SearchAdapter;
  basePath?: string;
  limits?: Partial<ServerLimits>;
  authorize?: (
    ctx: TContext,
    action: "status" | "index" | "search" | "searchAll" | "remove" | "clear",
    payload: unknown,
  ) => Promise<boolean> | boolean;
  logger?: SearchFnLogger;
};

Notes

  • authorize(...) runs before each handler and receives the parsed JSON payload when applicable.
  • limits controls payload size, query length, search fan-out, and indexing batch caps.
  • close() delegates to adapter.dispose() when the adapter implements it.