threadiverseUnified typescript client for threadiverse instances

One API for Lemmy and PieFed, with runtime-validated responses and fakes for consumer test suites.

🧙‍♂️

Automatic software detection

The instance's software is resolved via .well-known/nodeinfo and the matching provider (Lemmy v0, Lemmy v1, PieFed) is selected. Results are cached per hostname.

🛑

Runtime response validation

Every response is validated against a Zod schema. A response that doesn't match the canonical shape rejects with UnexpectedResponseError.

🛡️

Typed compat layers

Providers are type-checked against each software's official types (lemmy-js-client, PieFed's Swagger), so upstream API drift is a compile error.

🧪

Fake instances for testing

threadiverse/testing ships fake Lemmy and PieFed instances — seed content, inject errors, assert request payloads — with one API across providers.

📄

Uniform pagination

All list endpoints return cursor-based { data, next_page } responses, regardless of the underlying software's pagination scheme.

🔁

LemmyHttp-compatible API

Method names and payload shapes follow lemmy-js-client's LemmyHttp, so it is mostly a drop-in replacement.

Install

pnpm i threadiverse

import { ThreadiverseClient } from "threadiverse";

const client = new ThreadiverseClient("https://lemmy.world");

const { data: posts } = await client.getPosts();

WARNING

Early development stage: this project is under active development and may undergo significant API changes between versions. While v0, design decisions are guided by Voyager's usage.