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

expresso-api

v1.2.21

Published

An Express.js tool to statically analyze the backend, generating the specification for its routes using the OpenAPI standard.

Downloads

15

Readme

ExpressO

An Express.js CLI tool to statically analyze the backend, generating the specification for its routes using the OpenAPI standard.

How to install

npm install -g expresso-api

This will allow you to use the expresso command from anywhere.

Requirements

The project for which you wish to generate the OpenAPI specification should:

  • be an Express.js project;
  • be able to complete the start-up without any errors;

Commands — How to use

Generate

This command is used to generate the OpenAPI3.0 specification relative to an Express.js project by statically analyzing it.

Usage: expresso generate [--root] [--start] [--output] [--ext]

Description:

| Command | Alias | Description | Default | |------------|-------|-------------------------------------------------------------------------------------------------------------------------------|----------------------| | --root | | Specifies the root of the Express.js project to generate an OpenAPI specification for, defaults to current working directory. | process.cwd() | | --start | | The command line that will be used to start the project. | npm start | | --output | -O | Specifies a path of where to output the OpenAPI specification. | ./expresso-openapi | | --ext | -E | Specifies which format to use for the output between json and yaml. | json |

Test

This command takes as input another specification and compares it to the one that the tool generates.

Usage: expresso test <OAPIspec> [--root] [--start] [--output] [--ext]

Arguments

| Argument | Description | |------------|-----------------------------------------------------------------------------------------------------------------| | OAPIspec | Specifies the file path that points to the OpenAPI specification that the generated one will be tested against. |

Options' descriptions

| Command | Alias | Description | Default | |------------|-------|-------------------------------------------------------------------------------------------------------------------------------|----------------------| | --root | | Specifies the root of the Express.js project to generate an OpenAPI specification for, defaults to current working directory. | process.cwd() | | --start | | The command line that will be used to start the project. | npm start | | --output | -O | Specifies a path of where to output the OpenAPI specification. | ./expresso-openapi | | --ext | -E | Specifies which format to use for the output between json and yaml. | json |

Compare

Usage: expresso compare <OAPIspecA> <OAPIspecB> [--json]

Arguments

| Argument | Description | |-------------|------------------------------------------------------------------------------------------------------------| | OAPIspecA | Specifies the file path that points to an OpenAPI specification. | | OAPIspecB | Specifies the file path that points to a second OpenAPI specification that will be compared to OAPIspecA |

Options' descriptions

| Command | Alias | Description | Default | |----------|-------|----------------------------------------------------------------|---------| | --json | -J | Specifies to produce a JSON instead of a human readable report | False |

Known Issues

  • The response mining has issues with local identifiers. Global constants are self explanatory but local variables (e.g: status) does not say anything about the type of response.