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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sanity/embeddings-index-cli

v1.0.10

Published

CLI for creating and managing embeddings indexes

Downloads

691

Readme

Sanity Embeddings Index CLI

Using this feature requires Sanity to send data to OpenAI.com, and Pinecone.io for storing vector interpretations of documents.

CLI for the Sanity Embeddings Index API.

The Embeddings Index API enables creating named embeddings vector indexes.

An embeddings index contains embeddings for all Sanity documents matching a configured GROQ filter in a dataset. A GROQ projection is applied to matching documents before vectorization.

You can query indexes using semantic text search to obtain a list of matching document IDs sorted by relevance.

When an index is first created, all documents matching the configured filter are synced into the index. Creating an index can take time, depending on the number of existing documents and the indexer load.

Installation

npm i -D @sanity/embeddings-index-cli

Usage

 $ embeddings-index --help
 
 Usage
    $ embeddings-index [--help] [--debug] <command> [<args>]

   These are common commands for CRUD operations on embeddings indexes:

     create          Create a new embeddings index
     delete          Delete an existing embeddings index
     list            List all embedding indexes
     get             Get a specific embeddings index
     query           Query an embeddings index
     version         Show the currently installed version of Embeddings Index CLI

   Run the commands in a Sanity project directory with a 'sanity.cli.(ts|js)' file.

   Options
     --verbose       Log everything. This option conflicts with --silent
     --silent        Do not print info and warning messages. This option conflicts with --verbose
     --debug         Print stack trace on errors
     --version       Output the version number
     --help          Output usage information

See the individual commands for more, ie embeddings-index create --help.

Using with npx

Use npx @sanity/embeddings-index-cli in place of embeddings-index in the commands.

Example:

npx @sanity/embeddings-index-cli --help

License

MIT © Sanity.io

Develop & test

This plugin uses @sanity/plugin-kit with default configuration for build & watch scripts.

See Testing a plugin in Sanity Studio on how to run this plugin with hotreload in the studio.

Release new version

Run "CI & Release" workflow. Make sure to select the main branch and check "Release new version".

Semantic release will only release on configured branches, so it is safe to run release on any branch.