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

openapi-endpoint-trimmer

v2.0.1

Published

⚡ CLI Tool to Trim OpenAPI Paths / Endpoints ⚡

Downloads

1,278

Readme

openapi-endpoint-trimmer

⚡ CLI Tool to Trim OpenAPI Paths / Endpoints ⚡

Takes in a path to an OpenAPI spec, either as a file path or a URL, and outputs a new OpenAPI spec with only the paths you specify. The main use case for this is to trim an external spec to just the paths you need before you feed it through a code generator like openapi-zod-client.


I work for Akkio, a predictive AI platform geared towards Data Analysts. If you're looking for predictive AI without needing any data science knowledge, check us out!

Install

npm i -D openapi-endpoint-trimmer

Usage

This package is meant to be used as part of a package.json script.

A demo script is included in package.json that pulls the GitHub REST API's OpenAPI Spec, trims it to just a few endpoints, and runs it through openapi-zod-client to generate types. To run:

git clone https://github.com/andenacitelli/openapi-endpoint-trimmer
cd openapi-endpoint-trimmer
npm i
npm run demo

We do not have built-in output validation. We recommend you validate with @apidevtools/swagger-cli. This library isn't doing anything complicated, so shouldn't mess anything up, but is poorly tested and runtime validation is always a good idea.

CLI Flags

Usage: openapi-endpoint-trimmer [options]

OpenAPI Endpoint Trimmer.

Options:
  -i, --input <input>    Input File (Local or Absolute Path). (Required: Either this or --url).
  -u, --url <URL>        Input URL
  -o, --output <output>  Output File
  -p, --prefixes <path>     A comma-separated, zero-spaces list of path prefixes to keep. Anything starting with a prefix contained here will be kept. (Ex. /api/v1/users,/repositories)
  
  --help, -h                Display all flags, commands, and descriptions.
  --version, -v             Display the current version.

Implementation Details

This library is pretty straightforward behind the scenes.

  1. Loads the data in; local files use fs.readFileSync, URLs use undici.
  2. Parses the data into JSON using js-yaml.
  3. Filters through the paths attribute, keeping only the ones you have
  4. Outputs the JSON back to YAML using js-yaml.

Support

If you'd like to support me, you can support me with the "Sponsor" options on the right. Thank you for your support!

Contributing

I highly encourage contributions! Create issues and/or PRs for any bugs or features you'd like to see.

License

This project is licensed under the MIT license. This basically means you can use it for any purpose, commercially or not, but I have zero liability.