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-operations

v0.1.1

Published

Convert an OpenAPI spec into an array of Operations

Downloads

5

Readme

OpenAPI Operations

Build Status

A small (~1kb) library to transform an OpenAPI spec into an array of operations.

This opens up the use of higher order functions (map, filter, reduce, etc) to process the spec for your own needs.

Install

yarn install openapi-operations

Usage

const openApiOperations = require('openapi-operations')

// load and parse your OpenAPI spec, either remotely or from local file system in Node
const spec = await loadSpec()

// Convert the spec into an array of operations
const operations = openApiOperations(spec)

console.log(
  operations
    .map(op => op.id)
    .sort()
    .join('\n')
)

Options

Options {
  /**
   * The mode your tool will be operating in.
   *
   * Defaults to 'server'
   */
  mode: 'client'|'server'
  /**
   * Whether to include common top level spec information across all operations under the property `base`
   *
   * Defaults to false
   */
  includeBase: Boolean
}

mode

There are two perspectives when building OpenAPI tools, either delivering services from the server or consuming services from a client.

When on the server an API will potentially consume and/or produce specific formats of content.

On the client however these are inverted and more commonly known by the terms contentTypes and accepts. These align with the HTTP request headers Content-Type (the content format you're sending to the server) and Accept (the content format(s) you expect the server to respond with).

To choose your perspective you can define a mode.

mode === 'server' // default

  • operation.consumes
  • operation.produces

mode === 'client'

  • operation.contentTypes
  • operation.accepts

includeBase

An OpenAPI spec contains a number of top level details such as an info property with the spec title and description, or a securityDefinitions object defining global security options. These can be useful to access via an operation if you don't want pass around them separately.

Setting options.includeBase will add a shared base object to all operations which includes these top level properties.

Operation

Each operation is a plain JavaScript object with the following properties.

Operation {
  id: String
  method: String
  summary: String?
  description: String?
  basePath: String
  path: String
  fullPath: String
  url: String
  tags: Array<String>
  deprecated: Boolean?
  pathExt: Object?
  ext: Object?
  parameters: Array<Parameter>
  responses: Array<Response>
  security: Array<Security>?
}