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

dashing-reporter

v0.1.3

Published

Logs Continuous Integration metrics to Amazon DynamoDB.

Downloads

5

Readme

Dashing Reporter

Logs Continuous Integration metrics to Amazon DynamoDB.

Build Status

Installation

npm install dashing-reporter --save-dev

Usage

./node_modules/.bin/dashing-reporter --help

By default, dashing-reporter will use a local configuration and not attempt to connect to AWS.

To use a custom config, copy .dashingreporter.default.json to .dashingreporter.json to the root of your project and modify to meet your needs.

If you want to use Environmental Variables (and you should, because hard-coding credentials is a terrible idea), remove the corresponding settings from .dashingreporter.json and set them in your CI service.

| AWS Environmental Variable | .dashingreporter.json | |----------------------------|-------------------------| | AWS_ACCESS_KEY_ID | accessKeyId | | AWS_SECRET_ACCESS_KEY | secretAccessKey |

A working Travis CI configuration is included; see .travis.yml for details. This should theoretically work with Circle CI and others, but it hasn't been explicitly tested.

Payload

Each Item has the following attributes:

|Attribute|Description| |---|---| | branch | For builds not triggered by a pull request this is the name of the branch currently being built; whereas for builds triggered by a pull request this is the name of the branch targeted by the pull request (in many cases this will be master). |
| buildNumber | The number of the current build (for example, 4). | | commit | The commit that the current build is testing. | | coverageBranchesPercentage | Istanbul percentage of branches covered. | | coverageFunctionsPercentage | Istanbul percentage of functions covered. | | coverageLinesPercentage | Istanbul percentage of lines covered. | | coverageStatementsPercentage | Istanbul percentage of statements covered. | | eslintErrorCount | ESLint Error count. | | eslintWarningCount | ESLint Warning count. | | jobNumber | The number of the current job (for example, 4.1. | | language | Primary interpreting language name, like node_js. | | languageVersion | Primary interpreting Language version, like 6.7. | | repoSlug | The slug (in form: owner_name/repo_name of the repository currently being built (for example, fluxsauce/dashing-reporter) | | testResult | Set to 0 if the build is successful and 1 if the build is broken. | | timestamp | Current time in ISO 8601 formatted string. |

Local Development

Install DynamoDB locally.

If you have Homebrew installed, you can use the dynamodb-local formula.

brew install dynamodb-local

If you don't have Java:

brew cask install java

You have two options for running the DynamoDB server, with persistence:

dynamodb-local --sharedDb

The database will be stored in /usr/local/var/data/dynamodb-local.

Alternative, you can run it in memory with no persistence:

dynamodb-local --sharedDb -inMemory

Storage

For both hosted and local development, a DynamoDB table is required to store build metadata. The structure can be created with:

dashing-reporter --createTable