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

@cherrry-ai/cherrry-js

v1.0.5

Published

Isomorphic Javascript SDK for Cherrry

Downloads

6

Readme

cherrry-js

Cherrry Javascript SDK

App | Docs | Blog

Installation + API keys

npm package

Install the package from npm with your favorite package manager

npm install @cherrry-ai/cherrry-js

API Keys

From https://cherrry.com/dashboard/api to get your API Keys

Private Key

Private keys start with ch_prv

keep it secret and never use it client-side. It has service role privilages: it can read + write data.

Public Key

Public keys start with ch_pub

They're intended to be use client-side and have read-only privilages.

Initalize

const CherrryClient = require("@cherrry-ai/cherrry-js");

or

import CherrryClient from "@cherrry-ai/cherrry-js";

initialize the client

const client = new CherrryClient(api_key);

Concepts

Table

A table is a collection of documents.

Document

A document is respresented as a JSON object literal with three fields: text, image, and metadata. These fields are also JSON object literals, where the keys can be strings with any contents, and their values are also strings.

text and image are semantically searchable each by their type respectively. Each document must have either a text or image field. It can also have both fields. metadata is used to store additional information and for filtering (feature in progress), it is an optional field.

Basic Functions

Create Table

var { data, error } = await client.create_table("example_table");

Insert a Doc

Documents must be of the following form

{
    "text": {
        "a name for your text": "your desired text in a string"
    },
    "image": {
        "a name for your image": "a url to your downloadable image"
    },
    "metadata": {
        "key": "value"
    }
}

for example:

var { data, error } = await client.from("recipes").insert({
    text: {
        name: "Octopus Cherry Pie"
    },
    image: {
        preview: "https://i.imgur.com/lFC8p0L.jpeg"
    },
    data: {
        author_name: "Davy Jones",
        author_email: "[email protected]"
    }
});

Search

var { data, error } = await client
    .from("blogs")
    .search({ prompt: "sea creature desert", size: 1, search_type: "image" });

Get Doc by ID

The ID of documents are returned in the responses of /search or /doc

var { data, error } = await client.from("blogs").doc("1234");

Delete a Doc

var { success, error } = await client.from("blogs").delete("1234");