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

v0.4.1

Published

Basic parser for OpenAPI specs

Downloads

573

Readme

openapi-parse

Basic parser for OpenAPI specs. This is a thin wrapper around existing libraries. If you need more power/flexibility, check out Swagger/OpenAPI Parser, JSON Schema $Ref Parser, or swagger2openapi.

Installation

npm i openapi-parse

or

yarn add openapi-parse

Usage

import parse from 'openapi-parse'
// or const parse = require('openapi-parse').default

const options = { ... }
const specPathOrSchemaObject = ... // specify Swagger/OpenAPI spec path or a loaded schema object

const result = await parse(options)(specPathOrSchemaObject)

Options

| Option | Default Value | Description | | --------------------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | basePath | null | Used as the base path for relative references within the spec. | | dereference.mode | ['none'] | Set to an array of dereference modes. Possible mode values are none (no references will be dereferenced), external (only external references will be dereferenced), and all (both external and internal references will be dereferenced). The result will be an array of schemas, one for each mode specified. | | dereference.resolve | (original, result) => result[0] | After dereferencing, the result collection is passed to the specified resolve function. The resolve function also receives the original loaded schema, the return value will be used as the final dereferenced schema. | | upgrade.enabled | false | If enabled, OpenAPI 2.0 specs will be automatically upgraded to OpenAPI 3.0 using swagger2openapi. | | upgrade.options | {} | These options are passed down to swagger2openapi. More info. | | parser.canParse | fileInfo => false | Receives { path, extension, data } about referenced content. You can override and return true if you can parse the provided file information. More info. | | parser.parse | async fileInfo => {} | Receives { path, extension, data } about referenced content. You can override to implement a parser for the specified content. More info. | | resolver.canResolve | fileInfo => false | Receives { path, extension } about referenced content. You can override and return true if you are able to resolve the path. More info. | | resolver.resolve | async fileInfo => {} | Receives { path, extension } about referenced content. You can override to implement a resolver for the specified content. More info. |