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

swagger-paths

v1.0.5

Published

Match paths from a swagger file

Downloads

53

Readme

Swagger Paths

This package is basically a shrunken, zero-dependency, path matcher. This was heavily influenced (but is a complete rewrite, as of version 1) of Wikimedia's swagger-router.

Description

A simple

For example:

let swaggerPaths = require('swagger-paths')

let paths = swaggerPaths({
  '/': { data: 'root' },
  '/foo': 'this is foo',
  '/foo/{bar}': 123,
  '/{baz}': 'catch all'
})

Basically, construction requires an object keyed by path names with any value associated with it.

Paths are constructed using the normal OpenAPI 3 structure, with path variables wrapped in curly braces (e.g. {myVar})

Matching is performed calling the match(... path ...) function, for example:

paths.match('/')
// ... will return
// {
//   variables: {},
//   value: {
//     data: 'root'
//   },
//   path: Path {
//     path: '/',
//     pattern: '/',
//     variables: [],
//     components: []
//   }
// }

The object returned will include:

  • variables: an object including all the variables and their values resolved resolved when matching a path
  • value: the value associated with the path at construction
  • path: an internal structure indicating the path matched

The match(... path ...) method will return null in case of no matches:

paths.match('/foo/bar/baz')
// ... will return null

Another example:

paths.match('/foo/hello world')
// ... will return
// {
//   "variables": {
//     "bar": "hello world"
//   },
//   "value": 123,
//   "path": ...
// }

Note that calling with the path /foo/hello%20world (url-encoded version of the abolve example) will return the same (decoded) variable values.

Care is taken so that path components are re-encoded correctly both when constructing instances, and matching paths.

Finally, multiple occurrences of the slash character (or leading and trailing slashes) will be collapsed, henceforth a path such as /foo/bar will be effectively equal to:

  • foo/bar
  • /foo/bar/
  • ///foo///bar///

... and so on.

Arrays of paths

Construction can also happen with array of paths, for example:

let paths = swaggerPaths([
  '/',
  '/foo',
  '/foo/{bar}',
  '/{baz}'
])

In this case only variables will be resolved and the result will not have any value.