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

bee-script

v0.4.0

Published

Knex.js powered CLI for running scripts

Downloads

29

Readme

🐝bee-script🐝

A Knex.js powered script runner CLI tool

installation

npm install bee-script -g

description

bee script utilizes your local knex installation to intialize two tables bee_script_runs and bee_script_output

When you run a script using bee run it will create an entry in bee_script_runs and execute it in a forked node process. If there was any content written to stdout (console.log() etc.) by the script being run it captures that output in a text field on an entry in bee_script_output

At any point you can type bee history to see the most recently ran scripts and how they were run and their execution time

You can also use bee output to see recent output of ran scripts with the ability to dump the entire output content

Use bee to see all commands and their options for better usage.

bee options

Running

bee-script (for now) must be run from the directory containing your knexFile.js file. In addition to that you must also ensure knex (and the db drivers it needs) are installed in your project It uses that file to establish a connection to your DB instance and initialize/query its tracking tables

Type bee to see a list of all commands available to you

Roadmap

  • automatic knexFile.js discovery so running bee commands is less tedius
  • stats command to understand size and number of entries being used by bee-script
  • cleanup/delete command to delete rows of output/history we don't want
  • better ways for the template generated scripts to describe themselves
  • describe command to explain a given script and some details around it
  • a startup task creator to define a set of scripts to run with a bee script:startup command
  • a one time task creator (think knex migrations) to run scripts once and checks if they have been run already
  • slim down table output on commands to fit smaller terminal sizes better