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

denga

v1.0.2

Published

Agenda Dashboard

Downloads

5

Readme

Note: You must be using node version 10.15.x or greater to use denga :warning:.

A modern Agenda Dashboard made with :balloon: Angular :tada:

Features

  • Monitor jobs
  • Display jobs details
  • Display jobs stats
  • Filter jobs by name and your own search keys
  • Delete jobs by filter
  • Requeue and delete jobs
  • Auto refresh with "toggle switch" (on/off)
  • ... WIP :fire:

Install

$ npm install denga --global

Usage

$ denga --db mongodb://127.0.0.1:27017/denga 

Options

--db, -d: (required) connection URI used to connect to a MongoDB

--port, -p: (optional) server port, default 3000

--collection, -c: (optional) Mongo collection, same as Agenda collection name, default agendaJobs

--limit, -l: (optional) max number of jobs displayed, default 100

--title, -t: (optional) page title, default Denga

--keys, -k: (optional) (multiple) keys to include in search, you can use dot-notation (.) in a key to access nested properties

Examples

Example Usage 1

$ denga -p 3010 -c jobs -t myDashBoard --limit=300 -d mongodb://127.0.0.1:27017/denga

Example Usage 2

$ denga -p 3010 -c jobs --limit=300 -d mongodb://127.0.0.1:27017/denga -k id -k params.category

Consider the following jobs

{
    "name" : "jobTypeOne",
    "data" : {
        "id" : "sports",
        "params" : {
            "source_config" : {
                "from" : {
                    "amount" : 40,
                    "unit" : "minutes"
                },
                "query" : "foot OR soccer OR football"
            },
            "categories" : [ 
                "sports"
            ],
            "tags" : [ 
                "football"
            ]
        }
    },
    ...
}

{
    "name" : "jobTypeTwo",
    "data" : {
        "id" : "football",
        "params" : {
            "category" : "sports"
        }
    },
    ...
}
  • If you type in the search bar the keyword "sport" both jobs will be returned
  • If you type in the search bar the keyword "foot" only jobTypeTwo will be returned

If you want to be able to get both jobs by the keyword "foot", you need to add this key "params.tags"

Scripts

In your dev environment, you can kick off the project (server and client) under nodemon with

$ npm run monitor

you can launch an unmonitored process with

$ npm run all

to run build on both server and client-side

$ npm run build 

Project Structure

  • client (Angular)
  • server (Node.js)

Requirement

  • The Angular CLI requires a minimum Node.js version of either v10.13 or v12.0.

TODO

  • [x] Setup config system (config file and/or command line arguments )
  • [x] Display 100 jobs in home page
  • [x] Manage refresh
  • [x] Manage refresh "toggle switch" (on/off button)
  • [x] Display job details
  • [x] Make it run as NodeJS command-line package :sunglasses:
  • [x] Make jobs filtrable by name ( Prebuilt just front with Angular Material )
  • [x] Ship 1st release :pray: :rocket:
  • [x] Requeue and delete jobs
  • [x] Make sure to send the user filter in every query
  • [x] Make jobs filtrable by custom properties (~ get an array from config file)
  • [x] Display some stats
  • [x] Delete jobs by filter
  • [x] Keep the jobs filtred after a requeue or a delete
  • [ ] Create new job from UI
  • [ ] ...

Story

I'm a fan of Agenda :star: , and I'm using it in several projects for a very long time. And I've always used, Agendash as the dashboard, But I must say, it wasn't created to cover all the various situations (I've spent too many hours writing MongoDB queries).

So making Denga is a way to save some time.

License

GNU General Public License v3.0