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

testenv

v0.2.18

Published

A handy test environment that uses Karma/Webdriver/Mocha test runners for your client/server side unit/integration test and end-to-end test with light configuration and simple command lines.

Downloads

51

Readme

testenv

TravisCI

Install

npm i -D testenv
testenv init

Create Default Test Config File (Karma|Webdriver|Mocha)

testenv touch [<new-config-file-location>] [-k|-w|-m]

More about Karma Config File

More about Webdriver Config File

Run Custom Test Config File

testenv run [<config-file>]

Run Preset Test Config File

testenv run -c to run client side testings.

testenv run -s to run server side testings.

testenv run -e to run end-to-end testings.

testenv run -a to run all testings.

testenv run -u to run unit testings.

testenv run -i to run integration testings.

You could combine options [-u|-i] with options [-c|-s]. For example: to run client side unit testing.

Use testenv run -cu