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

freshjots

v1.0.2

Published

Tiny JavaScript client for the Fresh Jots API. Append-only notebooks for cron jobs, deploy scripts, and bots.

Downloads

534

Readme

freshjots — JS, TS, Windows CLI

Tiny JavaScript client for the Fresh Jots API. One file, zero dependencies (uses Node 18's global fetch).

CLI

Installing the package globally puts a freshjots command on your PATH, so you can read and write notes straight from a terminal without writing any JavaScript. This works in bash, zsh, fish, Windows PowerShell, and CMD — npm generates a .cmd shim on Windows automatically.

npm install -g freshjots

# Persist the token for every new shell (macOS defaults to zsh; use ~/.bashrc on bash):
echo 'export FRESHJOTS_TOKEN=mn_…' >> ~/.zshrc && source ~/.zshrc
# Windows PowerShell: [Environment]::SetEnvironmentVariable("FRESHJOTS_TOKEN", "mn_…", "User")

The CLI covers reading, writing, and organizing notes:

freshjots ls                              # prints "<id>\t<filename>\t<title>" per row
freshjots ls -n 10 --sort created         # last 10 by creation (--sort created|updated|appended)
freshjots ls --folder Work                # filter by folder id or name; --root for un-foldered
freshjots ls --all -l                     # every page, long format (id, updated, lock, folder, …)
freshjots get 42                          # full note as JSON
freshjots cat cron-jobs-prod              # note body, by id or filename
freshjots create "Research 2026 Q2"       # body from stdin or --body
freshjots append cron-jobs-prod "ok"      # text may also be piped on stdin
freshjots rm cron-jobs-prod               # delete by id or filename
freshjots mv cron-jobs-prod Work          # move into a folder (id or name); --root to un-folder
freshjots folders                         # prints "<id>\t<name>" per row
freshjots --version                       # print version (--help for full usage)

Both create and append read from stdin when the body or text isn't passed as an argument, so the usual pipe patterns work:

backup.sh && echo "backup ok $(date -Iseconds)" | freshjots append cron-jobs-prod
git log -1 --pretty=format:"%h %s" | freshjots append deploys

The same patterns work in PowerShell:

"backup ok $(Get-Date -Format o)" | freshjots append cron-jobs-prod
freshjots create "Deploy log" --body "Initial entry."

Exit codes: 0 on success, 1 on runtime errors (missing token, network failure, non-2xx API response — printed as Error: HTTP <status> <code>: <message>), 2 on usage errors.

Install

npm install freshjots

(Or pnpm add freshjots, yarn add freshjots, bun add freshjots.)

Use

import { Client } from "freshjots";

// Reads FRESHJOTS_TOKEN from the environment by default.
const client = new Client();

// Append text to a note (creates it if missing).
await client.append("cron-jobs-prod", "backup ok");

// Read a note's body.
const note = await client.note("cron-jobs-prod");
console.log(note.plain_body);

// List your notes (most recent activity first). Pass options to sort/filter:
const notes = await client.notes({ sort: "created", folderId: 3, limit: 20 });
for (const n of notes) console.log(`${n.id}\t${n.filename}\t${n.title}`);

// Create a note. The API derives the filename from the title — for a
// note addressable by an exact filename, use append() instead.
const created = await client.create({ title: "Research 2026 Q2", body: "Initial outline." });
console.log(created.filename); // server-derived stream name

Client methods: notes({ sort, folderId, limit, offset }), note(filename), noteById(id), create({ title, body }), append(filename, text), remove(id), move(id, folderId), and folders(). note()/noteById()/create() return the note object directly (no { note: … } wrapper); notes() and folders() return arrays. For notes(), sort is created|updated|appended and folderId may be a folder id or "none" (un-foldered only).

TypeScript

Types ship with the package — no @types/freshjots needed, no .d.ts to hand-write. Just import the typed surface:

import { Client, ApiError, type Note, type ApiErrorCode } from "freshjots";

const client = new Client();
const note: Note = await client.note("cron-jobs-prod");
//        ^? Note — full editor autocomplete on plain_body, byte_size, etc.

try {
  await client.append("log", "ok");
} catch (e) {
  if (e instanceof ApiError) {
    const code: ApiErrorCode = e.code; // narrowed union; exhaustive switches work
  }
}

Requires TypeScript 4.5 or later (anything that understands the "types" field in package.json's "exports" map).

Errors

Any non-2xx response throws ApiError with status, code, message, and (when present) details:

import { ApiError } from "freshjots";

try {
  await client.append("huge", "x".repeat(5_000_000));
} catch (e) {
  if (e instanceof ApiError) {
    console.log(`${e.status} ${e.code}: ${e.message}`);
    // 413 content_too_large: body exceeds the per-note 3 MB cap
  } else {
    throw e;
  }
}

Stable error codes: unauthenticated, forbidden, not_found, validation_failed, cap_exceeded, storage_cap_exceeded, content_too_large, content_type_mismatch, rate_limited. Full list: https://freshjots.com/docs.

Auth

Mint a token at https://freshjots.com/settings/api_tokens (Dev or Team tier required). Set it once:

export FRESHJOTS_TOKEN=<your-token>

Or pass explicitly:

new Client({ token: "mn_…" })

Requirements

Node.js 18 or later. Older versions don't have global fetch.

License

MIT.