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

@liquidweb-dev/annyong

v0.1.5

Published

`@liquidweb-dev/annyong` — typed HTTP request SDKs for two APIs maintained by Liquid Web:

Downloads

592

Readme

annyong

@liquidweb-dev/annyong — typed HTTP request SDKs for two APIs maintained by Liquid Web:

  • Liquid Web API (https://api.liquidweb.com) — supports HTTP basic auth or bearer tokens. Liquid Web publishes a bespoke docs format at /docs/json rather than OpenAPI.
  • Nocworx API — already publishes an OpenAPI spec.

The two SDKs are kept architecturally separate: there is no merged top-level surface, only sub-path imports.

Install (consumer)

npm install @liquidweb-dev/annyong
# or: bun add @liquidweb-dev/annyong
import { accountAuthToken } from '@liquidweb-dev/annyong/lw';
import { someNocworxOperation } from '@liquidweb-dev/annyong/nocworx';

How it's built

LW bespoke docs JSON  ─►  convert-liquidweb-openapi.ts  ─►  liquidweb-openapi.json ─┐
                                                                                     ├─►  @hey-api/openapi-ts  ─►  lw/  + nocworx/  ─►  tsc  ─►  dist/
Nocworx OpenAPI spec  ─────────────────────────────────────► nocworx-openapi.json ──┘
  1. Liquid Web → OpenAPI. convert-liquidweb-openapi.ts fetches https://api.liquidweb.com/docs/json and converts LW's bespoke types to OpenAPI 3.0.3 (liquidweb-openapi.json). Nocworx skips this step.
  2. OpenAPI → SDK. @hey-api/openapi-ts (configured in openapi-ts.config.ts) generates the typed SDK into lw/ and nocworx/.
  3. SDK → publishable package. tsc -p tsconfig.build.json emits .js + .d.ts to dist/. A postbuild script merges package-dist.json overrides into dist/package.json and copies README.md.

Dev commands

| Command | What it does | | --- | --- | | bun install | Install dependencies | | bun run generateLwOpenApi | Regenerate liquidweb-openapi.json from LW's docs | | bun run openapi-ts | Regenerate lw/ and nocworx/ SDKs from the OpenAPI specs | | bun run build | prebuild (clear dist/) + tsc emit + postbuild (write dist/package.json + copy README) | | bun run docs:dev | Start the docs site (Astro) at http://localhost:3000 | | bun run docs:build | Build the static docs site to docs/dist/ | | bun run docs:preview | Serve the built docs at http://localhost:3000 |

bun run generateLwOpenApi accepts flags after --:

bun run generateLwOpenApi -- --version <bleed|v1|...>   # default: bleed
bun run generateLwOpenApi -- --out ./liquidweb-openapi.json

If LW adds new bespoke types the converter doesn't recognize, the script logs them at the end of the run. Add real schemas to COMPONENTS (with constraints) or to STRING_TYPES (intentional plain-string fallback) in convert-liquidweb-openapi.ts.

Publish

The repo's root package.json is private: true. Publishing happens from dist/:

bun run build
cd dist
npm publish

dist/package.json is generated at build time from the merge of root package.json + package-dist.json, with scripts and devDependencies stripped.

Docs site

docs/ is a static Astro site that documents the SDK. It generates a page per operation (~1135), per named type alias (~414), and a per-operation playground that hits the API live via the SDK's client.

Source of truth for the docs is the generated SDK code itself (lw/gen/sdk.gen.ts + lw/gen/types.gen.ts), parsed at build time via the TypeScript Compiler API. Operations come from sdk.gen.ts (function name → method + URL); request/response shapes come from the type aliases in types.gen.ts walked into a uniform Node tree. JSDoc descriptions are preserved.

Build output is fully static (docs/dist/) — host on any CDN. Dev/preview server binds to port 3000 (so the LW dev API's CORS allowlist accepts it).

Stack

Bun + TypeScript + Astro (docs site). Generator: @hey-api/openapi-ts.