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

dry-test

v0.1.9

Published

The DRY Test Framework

Downloads

28

Readme

This is a test runner binary, it works on filename conventions. It's backed by mocha.

npm install dry-test

# dry-test [-v] [files] [--mocha [<mocha args>]]

The binary will pickup all files names *.test.js and .test.tjs in your current working tree. It ignores node_modules on the file tree walk. It will compile the .tjs (tamejs) files to hidden files, ie ..test.tjs in the same path as the original file. It will then pass all the files to mocha to test.

It does a walk of the file system every time, so I imagine it runs pretty slow with a bunch of test files on a conventional HD. If you do builds of anything, buy an SSD. Seriously.

By default it runs with qunit style tests and the dot reporter, however you can pass whatever args you want to mocha with the --mocha argument.