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

@civitas-cerebrum/wasapi

v0.0.3

Published

A lightweight REST API client library with fluent builder, typed responses, and decorator-based API definitions.

Downloads

442

Readme

Wasapi 🌶️

npm

Wasapi is a lightweight TypeScript REST API client library that simplifies HTTP service generation using decorator-based API definitions, a fluent builder, typed responses, and smart polling utilities.

The TypeScript counterpart of wasapi for Java — same design philosophy, native TypeScript experience.

Features

  • Decorator-based API definitions@GET, @POST, @PUT, @DELETE, @PATCH, @HTTP
  • Fluent builder — configure base URL, headers, timeouts, proxy, logging
  • Typed responsesApiCall<T>, ApiResponse<T>, ResponsePair<R, E>
  • Strict / lenient modes — throw on failure or return null
  • Response pollingmonitorResponseCode(), monitorFieldValue()
  • Zero HTTP dependencies — uses native fetch (Node 18+)
  • TC39 Stage 3 decorators — no experimentalDecorators, no reflect-metadata

Installation

npm install @civitas-cerebrum/wasapi

Quick Start

1. Define your API with decorators

import { GET, POST, DELETE, ApiCall } from '@civitas-cerebrum/wasapi';

interface User {
  id: string;
  name: string;
  email: string;
}

class UserApi {
  @GET('/users')
  getUsers(): ApiCall<User[]> { return null!; }

  @GET('/users/:id')
  getUser(pathParams: { id: string }): ApiCall<User> { return null!; }

  @POST('/users')
  createUser(body: { name: string; email: string }): ApiCall<User> { return null!; }

  @DELETE('/users/:id')
  deleteUser(pathParams: { id: string }): ApiCall<void> { return null!; }
}

2. Build the client

import { WasapiClient } from '@civitas-cerebrum/wasapi';

const api = new WasapiClient.Builder()
  .setBaseUrl('https://api.example.com')
  .setHeaders({ Authorization: 'Bearer token' })
  .setLogHeaders(true)
  .build(UserApi);

3. Execute requests

// Lenient mode (default) — returns null on failure
const users = await api.getUsers().perform();

// Strict mode — throws FailedCallException on non-2xx
const users = await api.getUsers().perform(true);

// Strict + log response body
const users = await api.getUsers().perform(true, true);

// Full response wrapper
const response = await api.getUser({ id: '5' }).getResponse();
console.log(response.status);    // 200
console.log(response.body);      // User object
console.log(response.headers);   // Record<string, string>

// Typed error handling
const pair = await api.getUser({ id: 'bad' }).getResponsePair(ErrorModel);
if (pair.isError()) {
  console.log(pair.errorBody);   // ErrorModel instance
}

API Reference

Decorators

| Decorator | Description | Method args | |-----------|-------------|-------------| | @GET(path) | HTTP GET | (pathParams?, queryParams?, options?) | | @POST(path) | HTTP POST | (body?, pathParams?, queryParams?, options?) | | @PUT(path) | HTTP PUT | (body?, pathParams?, queryParams?, options?) | | @PATCH(path) | HTTP PATCH | (body?, pathParams?, queryParams?, options?) | | @DELETE(path) | HTTP DELETE | (pathParams?, queryParams?, options?) | | @HTTP(method, path, hasBody?) | Custom method | positional based on hasBody |

Path parameters use :param syntax — e.g., /users/:id is substituted from pathParams: { id: '5' }.

Query parameters are appended as ?key=value from queryParams: Record<string, string>.

@HTTP — Custom HTTP Methods

For unconventional methods like PURGE, COPY, or LOCK:

import { HTTP, ApiCall } from '@civitas-cerebrum/wasapi';

class CacheApi {
  @HTTP('PURGE', '/cache/:key')
  purge(pathParams: { key: string }): ApiCall<void> { return null!; }

  @HTTP('REPORT', '/analytics', true)  // hasBody = true
  report(body: ReportRequest): ApiCall<ReportResult> { return null!; }
}

WasapiClient.Builder

| Method | Description | Default | |--------|-------------|---------| | setBaseUrl(url) | Base URL for all requests | required | | setHeaders(headers) | Default headers (merged per-request) | {} | | setTimeout(seconds) | Request timeout in seconds | 60 | | setLogHeaders(bool) | Log request headers | true | | setLogRequestBody(bool) | Log request body | false | | setDetailedLogging(bool) | Log response body | false | | setFollowRedirects(bool) | Follow HTTP redirects | false | | build(ApiClass) | Build typed API proxy | — |

Pass a ContextStore instance to the constructor to read defaults from configuration:

const store = new ContextStore();
store.put('wasapi.baseUrl', 'https://api.example.com');
store.put('wasapi.timeout', 30);

const api = new WasapiClient.Builder(store).build(MyApi);

ApiCall<T>

Every decorated method returns an ApiCall<T> — a lazy request descriptor that doesn't execute until you call one of its methods:

| Method | Returns | Description | |--------|---------|-------------| | perform(strict?, printBody?, ...errorModels) | Promise<T \| null> | Execute and return body. Strict throws on failure. | | getResponse(strict?, printBody?) | Promise<ApiResponse<T>> | Full response wrapper with status, headers, body. | | getResponsePair(ErrorClass) | Promise<ResponsePair<ApiResponse<T>, E>> | Response + typed error body. | | monitorResponseCode(code, timeout, interval?) | Promise<ApiResponse<T>> | Poll until HTTP status matches. | | monitorFieldValue(field, value, timeout, interval?) | Promise<T> | Poll until a response body field matches. | | clone() | ApiCall<T> | Independent copy for retry/polling. |

ApiResponse<T>

| Property / Method | Type | Description | |-------------------|------|-------------| | status | number | HTTP status code | | statusText | string | HTTP status text | | headers | Record<string, string> | Response headers | | ok | boolean | True if status 200-299 | | body | T \| null | Parsed JSON body | | rawBody | string | Raw response text | | isSuccessful() | boolean | Same as ok | | errorBody(ErrorClass?) | E \| null | Deserialize error body |

ResponsePair<R, E>

| Property / Method | Type | Description | |-------------------|------|-------------| | response | R | The API response | | errorBody | E \| null | Typed error body (null on success) | | isError() | boolean | True if errorBody is not null |

Exceptions

| Class | Description | |-------|-------------| | FailedCallException | Thrown in strict mode on non-2xx. Has statusCode, responseBody, url. | | WasapiException | General library error (timeout, missing config, etc.) |

Logging

Uses the debug package with wasapi:* namespace. Enabled by default.

# Suppress all wasapi logs
WASAPI_DEBUG=false npx tsx tests/my-test.ts

# Show only request logs
DEBUG=wasapi:request npx tsx tests/my-test.ts

Comparison with Java Wasapi

| Java (Retrofit) | TypeScript (this package) | |-----------------|--------------------------| | @GET / @POST annotations on interface | @GET / @POST decorators on class methods | | retrofit.create(Service.class) | builder.build(ServiceClass) — returns Proxy | | Call<T> | ApiCall<T> | | Response<T> | ApiResponse<T> | | ResponsePair<R, E> | ResponsePair<R, E> | | Caller.perform(call, strict, printBody) | apiCall.perform(strict, printBody) | | WasapiUtilities.monitorResponseCode() | apiCall.monitorResponseCode() | | Extend WasapiUtilities | No inheritance needed — all on ApiCall<T> |

Important Notes

Argument order matters. Body-bearing methods (@POST, @PUT, @PATCH) take (body, pathParams?, queryParams?, options?). Non-body methods (@GET, @DELETE) take (pathParams?, queryParams?, options?). TypeScript enforces this at compile time, but be careful when constructing calls dynamically.

perform() returns null in lenient mode for both empty successful responses (e.g., 204) and failed requests. If you need to distinguish these cases, use getResponse() which gives you the full ApiResponse<T> with status code.

Response body is a plain JSON object, not a class instance. ApiCall<User>.perform() returns a plain object shaped as User, not an instance of User with methods. This is standard TypeScript REST client behavior (same as axios, ky, etc.).

Timeout units: Builder's setTimeout() is in seconds. Polling methods (monitorResponseCode, monitorFieldValue) take milliseconds for timeout and interval.

FormData via options: To send multipart requests through the decorator path, pass formData in the options parameter:

const form = WasapiClient.getMultipartFromFile('./photo.jpg', 'avatar');
await api.uploadAvatar(undefined, undefined, { formData: form }).perform(true);

License

MIT