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

@frontal-labs/testing

v1.0.4

Published

Frontal testing utilities and helpers

Readme

@frontal-labs/testing

Test utilities for Frontal SDK packages — mock HTTP, test clients, response factories, and fixture builders.

Installation

npm install -D @frontal-labs/testing

Quick Start

import { createTestHttpClient, mockPageResponse } from "@frontal-labs/testing";
import { GraphService } from "@frontal-labs/graph";

const { http, mock } = createTestHttpClient([
  { method: "GET", path: "/graph/entities/user", body: mockPageResponse([]) },
]);

const graph = new GraphService(http);
await graph.use("user").list();

mock.expectCalled("GET", "/graph/entities/user");

API

createTestHttpClient

Creates a mock HTTP client with route matching.

import { createTestHttpClient } from "@frontal-labs/testing";

const { http, mock } = createTestHttpClient([
  { method: "GET", path: "/v1/health", body: { status: "ok" } },
  { method: "POST", path: "/v1/graph/entities", body: { id: "ent_123" } },
]);

mock.expectCalled("POST", "/v1/graph/entities");
mock.expectCallCount(2);

createTestClient

Creates a full FrontalClient with a mock fetch injected.

import { createTestClient } from "@frontal-labs/testing";

const { client, mock } = createTestClient([
  { method: "GET", path: "/v1/workflows", body: { items: [], total: 0 } },
]);

const workflows = createWorkflowsClient(client);

Response factories

import {
  mockPageResponse,
  mockErrorResponse,
  mockStreamResponse,
  mockFixture,
} from "@frontal-labs/testing";

// Paginated response helper
const page = mockPageResponse([{ id: "a" }, { id: "b" }], { total: 2 });

// Error response
const error = mockErrorResponse(429, "Rate limited");

// SSE stream
const stream = mockStreamResponse([
  { type: "data", data: { chunk: 1 } },
  { type: "done", data: {} },
]);

// Named fixtures
const agent = mockFixture("agent", { name: "test-agent" });

Fixture builders

import { buildAgent, buildEntity, buildWorkflow } from "@frontal-labs/testing";

const agent = buildAgent({ name: "order-ops" });
const entity = buildEntity("customer", { email: "[email protected]" });
const workflow = buildWorkflow({ name: "onboarding" });

Environment Variables

No environment variables are required. The test client operates entirely in-memory with no network calls.