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

openapi-automatons

v2.0.44

Published

[![CI/CD](https://github.com/openapi-automatons/openapi-automatons/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/openapi-automatons/openapi-automatons/actions/workflows/ci-cd.yml) [![codecov](https://codecov.io/gh/openapi-automatons/openapi-a

Readme

OpenapiAutomatons

CI/CD codecov semantic-release npm downloads

What is OpenapiAutomatons

This library is a generator using openapi file.

Requirements

Since v2 this package is ESM-only and requires Node.js >= 22. Use it from an ESM project (or import it dynamically). v1.x (CommonJS) remains available for older setups.

What code can generate?

| name | language | type | | ---- | -------- | ---- | | @automatons/typescript-client-axios | typescript | client (axios) | | @automatons/typescript-client-fetch | typescript | client (standard fetch) | | @automatons/typescript-client-react-query | typescript | client (TanStack Query hooks) | | @automatons/typescript-zod | typescript | schema (zod) | | @automatons/typescript-server-nestjs | typescript | server (NestJS) | | @automatons/typescript-server-nextjs | typescript | server (Next.js App Router) |

Get Started

  1. Install library to your project
yarn add -D openapi-automatons @automatons/typescript-client-axios
# or, for the dependency-free fetch client:
# yarn add -D openapi-automatons @automatons/typescript-client-fetch
  1. Create settings in your project root automatons.json
{
  "openapi": "openapi.yml",
  "automatons": [{
    "automaton": "@automatons/typescript-client-axios",
    "outDir": "src/clients"
  }]
}
  1. Add generate command your package.json
{
  "scripts": {
    "generate": "openapi-automatons"
  }
}

Automatons.json

| property | | type | required | description | | -------- | --- | ---- | -------- | ----------- | | openapi | | string | true | This is openapi path. It can be relative or absolute. Also, there is no problem with the url format.| | automatons | | array | true | This is the property that contains the module. | | automatons | automaton | string | true | This is the module name. You can embed your own module. It is also possible to include it with a relative path. | | automatons | outDir | string | true | This is the output directory of module. |

OpenAPI support

openapi-automatons reads OpenAPI 3.0, 3.1, and 3.2 documents (3.0 and 3.1 are schema-validated; 3.2 documents are accepted). The TypeScript client generators support:

  • Schema typesstring, number, integer, boolean, object, array, enum, allOf (rendered as an intersection), oneOf / anyOf (rendered as a union), and $ref. From JSON Schema 2020-12 (3.1): nullable via type: ["...", "null"] (and the 3.0 nullable), and const (a single-value literal). String formats date / date-time map to Date, and url to URL.
  • Operationsget, put, post, delete, options, head, patch, trace, plus the 3.2 query method and additionalOperations (arbitrary HTTP verbs).
  • Parameterspath, query, header, cookie, and the 3.2 querystring parameter (serialized as application/x-www-form-urlencoded).
  • Request bodiesapplication/json, multipart/form-data, application/x-www-form-urlencoded.
  • Security schemesapiKey (header / query / cookie), http (basic / bearer), oauth2, and openIdConnect.
  • Servers — server variables, and naming via the 3.2 name field (falling back to the x-name extension, then the URL).

Not supported yet

Webhooks, streaming media types (itemSchema / Server-Sent Events / JSON Lines), hierarchical tags (parent / kind), $self, the OAuth 2.0 device authorization flow, XML serialization, and discriminator mapping (oneOf / anyOf are emitted as a plain TypeScript union).