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

@seriouslag/nx-openapi-ts-plugin

v0.0.41

Published

πŸš€ Nx plugin for `@hey-api/openapi-ts` codegen.

Readme

@seriouslag/nx-openapi-ts-plugin

This plugin provides a generator and executor for generating and updating OpenAPI clients using the @hey-api/openapi-ts library. This can be tied in to automation and CI workflows to ensure your API clients are always up to date.

Installation

npm install -D @seriouslag/plugin-nx

Usage

Generators

openapi-client

Docs

This plugin provides a generator for generating OpenAPI clients using the @hey-api/openapi-ts library.

Run in interactive mode nx g @seriouslag/nx-openapi-ts-plugin:openapi-client

Options
  • name: The name of the project. [ string ] (required)
  • scope: The scope of the project. [ string ] (required)
  • spec: The path to the OpenAPI spec file. [ URI or string ] (required)
  • directory: The directory to create the project in. [ string ] (optional) (default: libs)
  • client: The type of client to generate. [ string ] (optional) (default: @hey-api/client-fetch) To specify a specific version of the client you can use @hey-api/[email protected].
  • tags: The tags to add to the project. [ string[] ] (optional) (default: api,openapi) The defaults tags will not be added to the project if you specify this option.
  • plugins: Additional plugins to provide to the client api. [ string[] ] (optional)
  • test: The type of tests to setup. [ 'none' | 'vitest' ] (optional) (default: none)
Example
nx g @seriouslag/nx-openapi-ts-plugin:openapi-client --name=my-api --client=@hey-api/client-fetch --scope=@my-app --directory=libs --spec=./spec.yaml --tags=api,openapi

Executors

update-api

This executor updates the OpenAPI spec file and generates a new client. The options for the executor will be populated from the generator.

Run nx run @my-org/my-generated-package:updateApi

Options
  • spec: The path to the OpenAPI spec file. [ URI or string ] (required)
  • name: The name of the project. [ string ] (required)
  • scope: The scope of the project. [ string ] (required)
  • client: The type of client to generate. [ string ] (optional) (default: @hey-api/client-fetch)
  • directory: The directory to create the project in. [ string ] (optional) (default: libs)
  • plugins: Additional plugins to provide to the client api. [ string[] ] (optional) (default:[])
Spec File Notes

If the spec file is a relative path and is located in the workspace then the containing project will be listed as an implicit dependency. The assumption is made that that project will generate the API spec file on build.

If the spec file is a URL then we fetch the spec during cache checks to determine if we should rebuild the client code.