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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@codeinkit/cli

v1.8.11

Published

code in kit cli tool

Readme

@codeinkit/cli

Usage

npx @codeinkit/cli init flows-server
npx @codeinkit/cli init flows-ws-server
npx @codeinkit/cli init flows-rest-server
npx @codeinkit/cli action <flow name> <action number> <data path>
npx @codeinkit/cli flow <flowName> <dataPath>

generate flows-server

A server based only structure that works with flows. With this template you can write http server, websocket, tcp socket, bot etc.

file structure

  • flows - a folder that hold the flows you have, the index will run through this folder and register the flows by the name of the file / folder. if a folder is present there has to be index.js file that the main file (same as require a folder in nodejs).
  • setup - this folder run the initial setup, for example express configuration should be put here.
  • index.js - this file run through the flows and register them after that it activate the routes.
  • routes.js - here you can write the routes related to the project, http routes, websocket etc.

@codeinkit/cli generate ws-flows-server

create a websocket server that work out of the box with client flows (ex: react-flows-client, angular-flows-client)

the file structure is the same as the flow-server but unlike the flow-server routes already written to support websocket and there is existing flow of allow_origin which allow all origins but can be change to support specific origins.

@codeinkit/cli

execute single action according to data in path

@codeinkit/cli flow

execute single flow

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT