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

kinto-cli

v0.2.11

Published

KintoHub CLI Tools

Downloads

9

Readme

Kinto-cli

cli to interface with kintohub api

  Usage: kinto [options] [command]

  Options:

    -v, --version              output the version number
    -h, --help                 output usage information

  Commands:

    init [options]             Initialize the base env
    view-config                view the config
    clear-config               remove all the saved config (need to do `kinto init` after)
    proxy [options] [appname]  proxy for kintoblocks inside the provided kintoapp
    apidocs [options]          validates/parse apidocs

Apidocs

kinto apidoc

Supports the following

-l for linting (no output file) -e <path> for ignoring (can have multiple)

The tool only spits out kinto-apidoc.json not a whole folder

Processing

Modify groups for @apiSuccess and @apiError to modify 200, 400 to Success_200 and Error_400, so it allows the user to use groups like @apiSuccess (200) in the code

Default Groups

add the following custom groups if non is specified

  • @apiParam adds Body as the default group
  • @apiHeader adds Header as the default group
  • @apiSuccess adds 200 as the default group
  • @apiFailer adds 400 as the default group

Validations

  • show the validation errors grouped by @apiName

Validates the following:

  • must have documentation in project
  • @api required http verb and url per endpoint
  • @apiName check uniqueness per project and required for each endpoint
  • @apiSuccess
    • check uniqueness per endpoint
    • check the group is numerical (can also be Success_<number>) or Session
  • @apiError
    • check uniqueness per endpoint
    • check the group is numerical or (can also be Error_<number>) or Session
  • @apiHeader
    • check uniqueness per endpoint
    • check if group is Header,Session or Config
  • @apiParam
    • check uniqueness per endpoint
    • check if group is Url,Body or QueryString

When validation fails, no file is gonna be outputted and the process will exit with error

Remote block Debug:

  • use example.localdebug.config.json as a local debug example config

  • to run kinto proxy with a config:

        kinto proxy -f app.config.json

TODOS:

  • can't check uniquness for the field name, apidoc parser merges the same field name
  • APIDOC-PARSER scope is not failing the app
  • can't validate require @apiName if non is provided apidoc generates one