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

deploynest

v0.0.2

Published

Programmatic API client for DeployNest.

Readme

DeployNest API Client

Programmatic, type-safe client for the DeployNest HTTP API. Built on Hono's typed client so requests stay in sync with the server route definitions.

Installation

Inside the DeployNest monorepo, the package is available as a workspace dependency:

bun add deploynest

Quick start

import { DeployNestClient } from "deploynest"

const api = new DeployNestClient("https://deploynest.app")

const result = await api.v1.servers.getServers("org_abc123")

if (result.success) {
  console.log(result.servers)
} else {
  console.error(result.message)
}

When used from the DeployNest web app, pass the current origin so requests stay same-origin and session cookies are sent automatically:

const api = new DeployNestClient(window.location.origin, {
  userAgent: "DeployNest/1.0.0",
})

API versions

Resource clients are grouped under version namespaces on DeployNestClient. Today only v1 is available:

| Namespace | Client | Methods | | -------------------- | ------------- | ----------------------------------------------------------------------- | | api.v1.servers | Servers | getServers, createServer, setupServer, deleteServer | | api.v1.credentials | Credentials | getCredentials, createCredential, generatePrivateKey, deleteCredential |

Future API versions will be added alongside v1 (for example api.v2) without breaking existing callers.

Configuration

import { DeployNestClient, type ClientOptions } from "deploynest"

const opts: ClientOptions = {
  bearerToken: "your-token", // optional Authorization: Bearer header
  userAgent: "MyApp/1.0.0",  // optional User-Agent header
}

const api = new DeployNestClient("https://deploynest.app", opts)

| Option | Description | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | baseURL | Deployment origin (e.g. https://deploynest.app or http://localhost:3000). Do not include /api — resource paths are appended automatically. | | bearerToken | Sets an Authorization: Bearer … header on every request. | | userAgent | Sets a custom User-Agent header on every request. |

Response shape

Every method returns a discriminated result. Check success before reading the payload:

// Success
{ success: true, servers: [...] }
{ success: true, credential: {...} }

// Failure
{ success: false, message: "Forbidden." }

Authentication

All endpoints require authentication. When the client runs in the browser against the same origin as the app, session cookies are included automatically.

For server-side or external scripts, pass a bearer token via ClientOptions.bearerToken.

Every organization-scoped method requires an organizationId. The API validates that the authenticated user has the appropriate organization permission before returning data.