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

@eldrajs/sdk

v0.2.2

Published

Framework-free client for the Eldra Web Studio public storefront API: CMS, catalog, cart, checkout handoff, orders, inventory. Types generated from your gateway's OpenAPI document and CMS schemas at build time.

Readme

@eldrajs/sdk

The client for the Eldra Web Studio public storefront API: CMS, catalog, cart, checkout handoff, orders, inventory. Framework-free — plain fetch, runs in a browser, in Node, in SSR, at the edge.

pnpm add @eldrajs/sdk
import { createEldraClient } from '@eldrajs/sdk';

const eldra = createEldraClient({ orgId: 'your-organisation-id' });
const { data } = await eldra.catalog.listProducts();

Types come from your gateway

The package ships no response types. Add the Vite plugin and they are generated into your project on every dev start and build, from the gateway you point at:

import { eldra } from '@eldrajs/sdk/vite';

export default defineConfig({
  plugins: [eldra({ orgId: process.env.ELDRA_ORG_ID })],
});

That writes .eldra/web-studio/ — your CMS schemas as types, the gateway's API contract as types, and a typed client wrapper — and from then on eldra.cart.get(id) returns the cart your gateway actually returns. Commit the folder; it is what your CI type-checks against, and the diff is how you see the API change. Without the plugin, responses are unknown and you name the type at the call site.

The full walkthrough is docs/getting-started.md.

Preview mode

Both createEldraClient and the Vite plugin accept previewToken as a string or callback and send it as X-Preview-Token. Configure each separately; the generator never embeds the token in its output. See preview mode for examples and header precedence.

What is in the client

| Group | Methods | | ----------- | ---------------------------------------------------------------------------------------------------------------------- | | catalog | listProducts, getProduct, listCategories, listCollections, getCollection, listCollectionProducts, search | | cms | list, get, getEntryByUniqueField, resolveEntryList | | cart | addItem, get, updateItem, removeItem, applyDiscount, removeDiscount | | checkout | handoffUrl | | orders | get, recover | | inventory | availability | | features | getOrganization, list, isEnabled, getCapabilities |

Every failed request throws EldraHttpError with status and the gateway's problem code. createCartSession and createOrderAccessTokens persist the cart id and order tokens without throwing where storage is unavailable.