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

nx-content-store-client

v1.0.5

Published

Public HTTP client SDK for the nx-content-store API

Readme

nx-content-store-client

Public HTTP client SDK for the nx-content-store API.

Use this package to talk to any compatible nx-content-store-server instance — whether hosted or self-hosted.


Installation

npm install nx-content-store-client

Quick start

import { createContentStoreClient } from 'nx-content-store-client';

const client = createContentStoreClient({
  baseUrl: 'https://your-store-server.example.com',
  storeId: 'my-store',
  secretKey: 'sk_...',
});

// Get content
const text = await client.content.get({ key: 'blocks/hero' });

// Set content
await client.content.set(
  { key: 'blocks/hero' },
  { content: '# Hello world', format: 'md' }
);

Config

interface ContentStoreClientConfig {
  baseUrl?: string;          // Base URL of the store server
  storeId?: string;          // Default store ID (can be overridden per call)

  publishableKey?: string;   // Sent as x-ncs-publishable-key
  secretKey?: string;        // Sent as x-ncs-secret-key (takes priority)

  fetchImpl?: typeof fetch;  // Optional custom fetch (default: globalThis.fetch)
  defaultHeaders?: Record<string, string>;
  timeoutMs?: number;
}

If both publishableKey and secretKey are provided, the secret key header is sent and the publishable key is omitted.


Client API

client.stores       // create, get, list, update, disable, archive
client.keys         // create, list, revoke
client.content      // get, getEntry, exists, set, delete, listKeys, listEntries
client.revisions    // list, get, activate
client.backends     // list, get, upsert
client.sync         // run, listRuns, getRun, compare
client.diagnostics  // ping

Auth headers

| Header | Sent when | |---|---| | x-ncs-publishable-key | publishableKey is set and secretKey is not | | x-ncs-secret-key | secretKey is set (takes priority over publishable) |


Error classes

All errors extend ContentStoreClientError which carries code and status.

| Class | When thrown | |---|---| | ContentStoreClientAuthError | HTTP 401 or 403 | | ContentStoreClientConflictError | HTTP 409 | | ContentStoreClientValidationError | HTTP 400 or 422 | | ContentStoreClientHttpError | All other non-2xx responses |

import {
  ContentStoreClientAuthError,
  ContentStoreClientConflictError,
} from 'nx-content-store-client';

try {
  await client.content.set({ key: 'k' }, { content: '...', expectedHash: 'old' });
} catch (err) {
  if (err instanceof ContentStoreClientConflictError) {
    console.log('Hash mismatch:', err.code, err.status);
  }
}

Response envelope

The client expects and parses the standard server envelope:

// Success
{ ok: true, data: T, meta?: { requestId?: string } }

// Error
{ ok: false, error: { code: string, message: string }, meta?: { requestId?: string } }

Package boundary

This is a pure HTTP client. It has no dependency on:

  • nx-content-store-server (the deployed service)
  • xronox-content-store (private persistence layer)
  • nx-content (git/file backend)
  • MongoDB or any storage

It only uses fetch and its own types.


License

UNLICENSED