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

report-viewer

v0.3.3

Published

Cli for piping a unit test result directly into your browser

Downloads

63

Readme

report-viewer

A cli for piping a unit test result directly into your browser. Currently only works with mocha and the spec reporter.

Each time a test result is piped into stdio, the browser view will be updated. Uses socket.io for best experience.

No livereload needed. Errors will be shown prominently on top.

The console output will be visible in the side of the browser

Install

npm install report-viewer

Usage

Best used with mocha:

mocha --watch 2>&1 | report-viewer --opener

or

report-viewer --opener 'mocha --watch'

Both will start a webserver (localhost:9999) to view current testresults. The later one will be able to restart mocha through the webview.

Available options:

-h, --help                output usage information
-V, --version             output the version number
--port <n>                port
--opener                  opens a browser
--viewer <(module-)name>  loades a specific viewer

From node

runner = require("report-viewer")
mocha = require.resolve("mocha")+"/bin/mocha"
path = require("path")
specs = path.resolve(__dirname, './test')

runner({
  port: process.env.PORT, # Heroku uses dynamic port assignment
  args: mocha + ' ' + specs
})

Views

You can use your own view by cloning the report-viewer-default repository, rename and change it. both should work:

mocha --watch 2>&1 | report-viewer --viewer your-view
mocha --watch 2>&1 | report-viewer --viewer /path/to/your-view

If you publish your work, let me know, I will link it up

Testing

See the report-viewer-tester repository

Release History

  • v0.3.0: moved the parser into the view

    is now able to spawn mocha on its own, allows restarts

  • v0.2.0: reworked the view

    using spec reporter now

    works with debug and console output directly into the browser window

  • v0.1.1: modified dependencies

  • v0.1.0: Moved the view into seperate bundle report-viewer-default

    Largely improved the view

    Console output is piped into the console of the browser

    Cut on dependencies

  • v0.0.2: Rename to report-viewer

  • v0.0.1: First Release

License

Copyright (c) 2015 Paul Pflugradt Licensed under the MIT license.