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

@messijo/sdk

v0.3.0

Published

Experimental TypeScript SDK for the Messijo API.

Readme

@messijo/sdk

Experimental, Fetch-based TypeScript SDK for the Messijo API.

Install

npm install @messijo/sdk

This package is ESM-only.

Quick start

import { createMessijoClient } from '@messijo/sdk';

const messijo = createMessijoClient({
  apiKey: process.env.MESSIJO_API_KEY!,
});

const { data } = await messijo.listKeywords({
  path: { org_id: 'organization-id' },
});

The client defaults to https://api.messijo.com and sends the API key in the X-API-Key header. Keep API keys out of source control, logs, URLs, and public browser bundles.

Pass baseUrl and fetch when testing or supplying an instrumented standards-compatible Fetch implementation:

const messijo = createMessijoClient({
  apiKey: process.env.MESSIJO_API_KEY!,
  baseUrl: 'https://api.example.test',
  fetch: instrumentedFetch,
});

Named operations and their request and response types are exported from the package entry point. Consumers do not need generated internal imports.

Errors

Non-success responses and transport failures throw MessijoApiError. Response errors expose status, response headers, safely parsed response data, and redacted request method/URL metadata. Transport errors retain the original error as cause.

import { MessijoApiError } from '@messijo/sdk';

try {
  await messijo.getOrganization({
    path: { org_id: 'organization-id' },
  });
} catch (error) {
  if (error instanceof MessijoApiError) {
    console.error(error.status, error.data);
  } else {
    throw error;
  }
}

Supported environments

Supported environments are Node.js 22 and 24 and browser environments with Fetch, Headers, AbortController, and Web Streams. The package is ESM-only and ships declarations tested with TypeScript 6 and 7.

Deno, Bun, CommonJS-only applications, React Native, and legacy browsers are not currently supported.

Experimental compatibility

The SDK is pre-1.0. Minor versions may include documented breaking changes, and SDK versions are independent from API contract versions. Pin a specific version and review the changelog before upgrading.

Each release records the API contract, backend source commit, OpenAPI checksum, generator version, and SDK commit. Release 0.1.0 was the one-time authenticated package bootstrap and does not have GitHub OIDC provenance. Subsequent releases use npm trusted publishing and automatic provenance from the protected repository workflow.

Development, generation, and release guidance is available in the SDK repository.