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

@ocelot-consulting/swagger

v1.1.0

Published

The Swagger command-line. Provides Swagger utilities and project lifecycle support.

Downloads

8

Readme

Ocelot Consulting Swagger Editor

What

A wrapper around swagger-editor that persists changes to the source yaml file

Why

The official npm swagger module hadn't had a release in over 2 years, the editor was still using the old swagger editor and ui, and it was becoming painful to try and edit larger swagger files in it (plus the look and feel was a bit dated).

Originally this project was going to be a fork of the npm swagger module with the goal of updating the UI, but the changes in the swagger-editor project were too great to allow for any reuse of the current codebase.

Installation

npm i -g @ocelot-consulting/swagger

Usage

  • Navigate to the root of your project
  • A package.json file is required
  • package.json either needs to be in the directory that o-swagger runs from, or by passing --package /relative/or/absolute/path/to/package.json
  • By default, a swagger.yaml is expected to be located at ./api/swagger/swagger.yaml relative to the root of your node project.
  • You can override the default by passing --fileName ./relative/path/to/swagger/file.yaml
  • Execute o-swagger edit to start the editor process and automatically open the editor ui in your default browser

Changes to the yaml are persisted back to the source file as long as the editor process keeps running.