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

spec-dts

v0.1.0

Published

OpenAPI type inference without the codegen

Downloads

66

Readme

Spec-dts

Spec-dts enables inferring the types from an OpenAPI spec without any code generation – just good old TypeScript type inference.

npm i spec-dts

Features

  • [x] Infer OpenAPI types from a JSON spec
  • [x] No code generation
  • [x] Simple API and usage

Example Usage

import { ParseSpec } from "spec-dts";

// Import from file
import type { Spec } from "spec.d.ts

// Or:
type Spec = {
    // JSON spec here
};

type Api = ParseSpec<Spec>;

type GetPostsResult = Api["GET /posts"]["Output"]

Table of Contents

Why?

When consuming APIs that offer an OpenAPI spec, we're forced to use bloated code generators which rarely fit our needs and frequently get in the way, undermining the utility of OpenAPI specs. Spec-dts offers a lightweight, types-only approach for utilising contracts defined in OpenAPI specs.

How?

By representing an OpenAPI spec in .d.ts form, we can run type inference on it directly, without any code generation.

API Reference

ParseSpec<T>

Derive an API definition from an OpenAPI Spec

We can directly infer the types of a JSON OpenAPI spec using the ParseSpec<T> type utility.

type API = ParseSpec<{
  // OpenAPI JSON
}>;

type GetPostsOperation = API["GET /posts"];
// { Query, Params, Headers, Body, Output }

We can directly paste in the OpenAPI contents here, considering JSON constitutes a valid TypeScript type.

More Scalable Approach

Manually pasting the document will suffice for many applications, but if we want to make this more automatic, we can simply fetch our OpenAPI document and save it in a spec.d.ts file (or any other name).

A simple unix shell script to do this could look like:

curl -s "<your-openapi-url>" |\ # Get openapi spec
 	sed 's/`/\\`/g' |\ # Escape backticks
  awk '{print "export type Spec = `"$0"`;"}' >> spec.d.ts # Save to file

ParseX<T>

On top of parsing the entire spec, we can parse individual parts, like schema, params or operations. These are the internally used types used to parse the spec as a whole.

import {
  // Schema
  ParseSchema,
  ParseSchemaObject,
  ParseSchemaReference,

  // Primitives
  ParseObject,
  ParseArray,
  ParseString,
  ParseBoolean,
  ParseNumber,
  ParseNull,
  ParseUnion,
  ParseIntersection,

  // Parameters
  ParseParameter,
  ParseParameters,
  ParseParameterReference,
  ParseParameterObject,

  // Body/Response
  ParseBody,
  ParseResponse,
  ParseResponses,
  ParseBodyOrResponseReference,
  ParseBodyOrResponseObject,

  // Operations
  ParseOperation,
  ParsePath,
} from "schema-dts";