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

ariel

v0.0.9

Published

continuously test and cover files using mocha and coveraje. Note: ariel requires an index.js in root as entry point for now.

Downloads

10

Readme

Ariel

As in 'The Tempest' Ariel is a the magicians eyes and ears, dutifully watching code and listening to coverage going up and down.

Getting Started

npm install ariel

create a mocha.opts file in your local 'test' directory. Should look something like

--require should 
--reporter tap
--ui bdd
--growl

if you want to write and test coffee-script then do

npm install coffee-script 

create an index.js importing all relevant modules from your lib folder. These will be inspected for coverage. write your mocha tests in the 'test' directory. You can write them in coffee script or javascript.

start ariel from "node_modules/.bin"

or if you have ./node_modules/.bin" in your path then just type:

ariel

Running

When ariel starts it compiles all coffee files into js files in order to allow for coverage and easier debugging (line number matches and coffee compiler issues). These automatically compiled files are deleted when ariel is exited (CTRL-C). It will recompile whenever a change is detected to a coffee file.

Whenever a test is detected or a change to any source file is detected a re-run of all tests is initiated and coverage is recalculated.

You can look at coverage in the webbrowser. The url is written to the console. only files included from index.js in the root are covered, so make sure you require them from there.

Command Line Arguments

--cc or --coverageConsole will output coverage to the console as a single metric instead of starting the server

Based On

The awesome coveraje (had to bundle it though since i had to make a minor change which i will try to push into the original) mocha optimist ...

Build Status

Other tools that might come in handy

Growl (Windows) with Risor installed is very helpful. I like Risor because i find it more apparent and yet unobtrusive than getting a similiar bar from the top :). Dont forget to install growlnotify on windows (i also put it into dev-tools though.)