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

@verusuite/api

v1.1.0

Published

Client for the VeruSuite API: mail, calendar, contacts, documents, spreadsheets, files and workspace administration.

Readme

@verusuite/api

TypeScript and JavaScript client for the VeruSuite API.

npm install @verusuite/api

Needs Node 18 or later. The package ships compiled JavaScript alongside its type declarations, so a JavaScript project imports it exactly as a TypeScript one does and gets the autocomplete anyway. It reaches for no Node built-ins, only fetch and AbortController, so it also runs in Deno, Bun, Cloudflare Workers and anything a bundler targets.

It is a server-side client. An API key in a browser bundle is a key you have published.

Install it from npm rather than from git: npm looks for package.json at the repository root, and this package lives in node/.

Use

import { VeruApi, VeruApiError } from "@verusuite/api";

const api = new VeruApi({ apiKey: process.env.VERUAPIS_KEY! });

const folders = await api.mail.listFolders();

try {
  await api.mail.send({
    to: ["[email protected]"],
    subject: "Nightly report",
    text: "All green.",
  });
} catch (err) {
  if (err instanceof VeruApiError && err.isPermissionProblem) {
    console.error(`This key is missing a permission: ${err.code}`);
  }
}

The envelope is unwrapped for you. Use requestEnvelope when you want the request id or the pagination cursor.

Paging

for await (const message of api.mail.messages({ folder_id })) {
  console.log(message.subject);
}

Cursor rather than page number: rows arriving mid-walk shift an offset and would make a page get skipped.

What it does for you

  • Idempotency. Every write carries an Idempotency-Key unless you supply one, so a retry cannot send the same email twice.
  • Retries. Only on 429, 408 and 5xx, with the server's Retry-After when it sends one, and exponential backoff with jitter otherwise. A 400 or a 403 is never retried; it will fail the same way every time.
  • Errors. VeruApiError carries code, status, requestId and any field details. Branch on code, never on message, which is written for a person and may be reworded.

Anything not wrapped yet

request() reaches every endpoint, wrapped or not:

const settings = await api.request("GET", "/v1/mail/settings");

Types

Written by hand, in src/types.ts. Nothing here is generated, and the drift that would otherwise cost is checked instead:

npm test          # unit tests, with coverage
npm run check-spec