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

@aspected/ts-sdk

v0.2.1

Published

TypeScript SDK for the Aspects.dev vector index API

Readme

@aspects/sdk

TypeScript SDK for the Aspects.dev vector index API — a database that supports sparse vector queries where some dimensions of the search vector may be left undefined.

Installation

npm install @aspects/sdk

Quick Start

import { AspectsClient, AspectsApiError } from '@aspects/sdk';

const client = new AspectsClient({
  basePath: 'https://api.aspects.dev',
  apiKey: 'your-api-key',
});

Usage

All API methods are available directly on the client — no need for sub-namespaces.

Indexes

// List all indexes
const { data } = await client.listIndexes();

// Create an index
await client.createIndex('my-index', {
  aspects: [{ name: 'color' }, { name: 'size' }],
  hnsw: { m: 16, efConstruction: 200 },
});

// Get index details
const index = await client.getIndex('my-index');

// Search an index
const results = await client.searchIndex('my-index', {
  query: { color: [0.1, 0.9, 0.3] },
});

// Delete an index
await client.deleteIndex('my-index');

Documents

// Upload documents
await client.uploadDocs('my-index', {
  data: [
    { id: 'doc-1', aspects: { color: [0.1, 0.9, 0.3], size: [0.5] } },
    { id: 'doc-2', aspects: { color: [0.8, 0.2, 0.1] } },
  ],
});

// Get a single document
const doc = await client.getDoc('my-index', 'doc-1');

// List documents
const docs = await client.getDocs('my-index');

Error Handling

HTTP errors are automatically parsed and thrown as AspectsApiError with the server's error message:

import { AspectsApiError } from '@aspects/sdk';

try {
  await client.getIndex('nonexistent');
} catch (err) {
  if (err instanceof AspectsApiError) {
    console.error(err.message);  // Server error message
    console.error(err.status);   // HTTP status code (e.g. 404)
    console.error(err.response); // Parsed ErrorResponse object
  }
}

Configuration

The client accepts all standard configuration options:

const client = new AspectsClient({
  basePath: 'https://api.aspects.dev',  // API base URL
  apiKey: 'your-api-key',               // API key authentication
  headers: { 'X-Custom': 'value' },     // Custom headers on every request
  middleware: [/* custom middleware */], // Additional middleware
  fetchApi: customFetch,                // Custom fetch implementation
});

Development

Regenerate the SDK from the OpenAPI spec

npm run generate

Build

npm run build

Publishing

In order to publish a new version of the SDK, there are a few steps to follow:

  1. Update the version number in package.json according to semver rules.
  2. Build the SDK using npm run build.
  3. Ensure you have an npm account and are logged in via the command line (npm login), or are using the .npmrc file with the correct auth token.
  4. Publish the package to npm using npm publish.

License

MIT