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

@releaseotto/core

v0.2.0

Published

OTTO performs your action on new versioning of APIs, packages, schemas, etc. Keepings things nice and neatly automated.

Downloads

2

Readme

Otto

This library is build for auto-generation, i.e. something changes version, some action is performed, and the version meta data is then saved either locally or remotely for next time it's time to run again.

Use cases

  • AsyncAPI JSON Schema library updates (completely independent), triggers a re-generation of auto-generated models representing AsyncAPI as parser models.
  • AsyncAPI document changes version, triggers a re-generation of libraries enabling 3 lines of code to call.

Supported dependencies (version checks)

This stage is all about finding the version of "something" (API version, library version, etc), that will be used to figure out if it's changed.

Version Retrievers

  • github-repository
    • specific branch
    • reading file i.e. package.json
  • github-releases
    • specific version match

Version Meta retrievers

  • github-repository
    • local file
    • in specific branch

Actions

This stage is all about performing some action, once it figures out if the version changed.

This could for example be generating code with

  • Modelina
  • AsyncAPI generator

Initialize

This stage is used to define a behavior for when the repository of the automation does not yet exist. If the library detects this it helps you set it up based on the configuration.

Initializers:

  • GitHub Template
    • This lets you use a GH template as starting point, and then allow you to make additional changes to the repository, before continuing with it's automation.