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

make2tap

v0.1.3

Published

Leverage TAP to transform your ugly make outputs into nice readable ones

Downloads

5

Readme

make2tap

Build Status Code Climate Test Coverage

Leverage TAP to transform your ugly make outputs into nice readable ones using any TAP reporter like tap-spec or tap-dot.

Usage

Assuming make2tap is in your path (using npm scripts), simply pipe make output to it

Assuming this is your makefile

clean:
	## Clean
	# remove /dist
	@rm -rf dist

build:
	## Build js files
	# compile to js
	@echo 'compile output...'
	# minify
	@echo 'minify output...'

Then

make clean compile 2>&1 | make2tap

Note: 2>&1 is quite important here, it allows make stderr stream to be piped to make2tap as well so we can handle errors.

Ouputs:

TAP version 13
# Clean
ok 1 - remove /dist
TAP version 13
# Build js files
ok 2 - compile to js
compile output...
ok 3 - minify
minify output...
1..3

Of course, you should pipe it to the TAP reporter of your choice:

make clean build | make2tap | tap-spec

tap-spec

Comment syntax

make2tap understand a few kinds of lines:

  • ## Task title: as a TAP Diagnostic, aka a section, or title
  • # Step name: as a TAP test line, which will use a single step
  • anything else: as regular output, not handled as part of the result but still shown, will us it to show commands output.

You'll probably want to structure your makefile as such:

build:
	## Build js files

	# compile to js
	@echo 'compile output...'

	# minify
	@echo 'minify output...'