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

puny

v2.0.2

Published

The bantamweight JavaScript test runner with no dependencies

Downloads

21

Readme

puny

The bantamweight JavaScript test runner with no dependencies

No dependencies? Are you sure?

Yes, and Puny is just 30 lines of human-readable JavaScript including helpful error messages and colorized, indented output. Puny simply leverages:

  • Node's powerful Assert library
  • The beauty of arrow functions
  • try->catch
  • ANSI escape codes

But Puny is bad right?

If you still want to use a big test module that you don't use most of, more power to you. Mocha's custom utils file alone is 746 lines of code, so you might want to start there.

Make testing huge again

Is it universal?

Yes. Puny will even work in the Browser if you package it with the optional Assert library available in NPM.

Running a test looks like this:

const run = require('puny')
const Localization = require('./src/Localization')

const localization = new Localization({ messages : { foo : 'Foo the foos. Also %s & %s.' } })

const tests = [() => [
    'When localizing with a key present in `this.props.messages`',
      localization.localize('foo', 'bars', 'bazzes'),
      'should equal',
      'Foo the foos. Also bars & bazzes.'
], () => [
    'When attempting to localize with a key absent in `this.props.messages`',
      localization.localize('BAR', 'bars', 'bazzes'),
      'should equal',
      'BAR bars bazzes'
]]

run(tests)

Is there a catch?

Not really. Puny even gives you useful error messages when you don't use it correctly. Puny eats its own dogfood too—the tests for Puny are written using Puny. Puny tests itself!

Can I easily extend Puny?

Sure you can. Puny accepts a second parameter named logger that you can use to intercept the default output mechanism to replace it with your own. You could use this to print Puny's messages to the DOM, send it to an API or feed it to Socket.io. It's up to you! Here's a toy example:

const run = require('puny')

const tests = [/* ... */]

run(tests, function customLogInterceptor (...args) {
	const logArea = document.querySelector('section#log-area')
	const logTextNode = document.createTextNode(args.toString())
	logArea.appendChild(logTextNode)
})

Wait, were you really serious about all this?

Not really.