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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rachelambda/well-rested

v0.1.3

Published

A typescript package for defining well-typed restful APIs

Downloads

8

Readme

🛏️ Well Rested 🛏️

Rest well knowing your REST API is correctly typed!

well-rested is a typescript package which lets you define input and output types for REST APIs, and then checks that all requests made matches said types.

Features

  • Allows fully defining input (http parameter, and request body) types as well as response types, per endpoint.
  • Checks that endpoint exists when type-checking request, in some cases the type system may even be able to figure out the possible endpoints for usage in e.g. completion.
  • Checks that all needed arguments are given and are of the right type when checking a request.
  • Gives information about return type when checking a request.
  • Lightweight with zero runtime dependencies, leveraging portable builtin functions and asynchronus requests.
  • Gives complete Response object if HTTP request fails, for flexibility and error inspection.

Usage

Installation

npm i @rachelambda/well-rested

Usage

  • Ensure to use either the bundler or nodeNext options for moduleResolution in your tsconfig.json in order to follow the following example.

In order to define an API you simply define a type which extends the APIDef interface, and create an instance of the API class using it as a generic argument.

API.ts

import { API } from '@rachelambda/well-rested'

type MyAPI = {
  "/foo/bar": {
    kind: "GET",
    query:    { id : number },
    response: { name: string },
  },
  "/foo/time": {
    kind: "GET",
    response: { date: string },
  },
  "/foo/login": {
    kind: "POST",
    request:  { user: { name: string, password: string } },
    response: { accessToken: string } | { error: string },
  },
  "/foo/post": {
    kind: "POST",
    query: { postid: number },
    request:  { accessToken: string },
    response: { result: string } | { error: string },
  },
}

export const myApi = new API<MyAPI>("http://localhost:8000")
export default myApi

You can then make requests in other files as such foo.ts

import { myApi } from './API.js'

const barResponse : { name: string } | Response = await myApi.get("/foo/bar", {
  query: { id: 5 }
})

console.log(barResponse)

const dateResponse : { date: string } | Response = await myApi.get("/foo/time", {})

console.log(dateResponse)

const loginResponse : { accessToken: string } | { error: string } | Response = await myApi.post("/foo/login", {
  request: { user: { name: "bunger", password: "cat" } } 
})

console.log(loginResponse)

const postResponse : { result: string } | { error: string } | Response = await myApi.post("/foo/post", { 
  query: { postid: 42 },
  request: { accessToken: "so_secret" } 
})

console.log(postResponse)

this example was taken from tests/index.ts

Quirks

If you try to use a non-exitsing endpoint, or try to post a get endpoint or vice versa you will get an error like Argemunt of type '...' is not assignable to parameter of type 'never', this is intentional and stops you from missusing endpoints.