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

testrumenter

v0.0.15

Published

Command-line utility to test JavaScript code instrumenter

Downloads

6

Readme

Testrumenter

Command line utility for testing, benchmarking and debugging JavaScript code instrumenter. Install with:

npm install -g testrumenter

Instrumenter File

An instrumenter file is a CommonJS module which exports a function transforming javascript code. For instance, the instrumenter below replaces the literals "foo" by "bar":

module.exports = (script) => script.replace(/"foo"/g, "\"bar\"");

An instrumenter directory is a directory where every .js file is an instrumenter file.

Target File

Target file should contain plain JavaScript code. To avoid interference between target files, they shoyld not have any effect on the global object. So if variables are needed, you should use the module pattern (function () { ... } ()) or let/const. There exists shortcuts for accessing predefined targets:

A target directory is a directory where every .js file is a target file.

Commmand Line Interface

Testrumenter uses stderr, so stdout can be redirected to /dev/null to avoid poluting terminals logs. Color scheme:

  • cyan: information.
  • green: test success.
  • yellow: test failure, stop the execution (not for test suite).
  • majenta: failure due to instrumenter, stop the execution.

Test

Test a instrumenter file on a target file.

testrumenter instrument.js target.js

Test Suite

Test suite an instrumenter file on a target directory. Errors thrown while evaluating instrumented targets do not preclude the test suite from finishing.

testrumenter instrument.js target

Cross Tests

Cross-test an instrumenter directory on a target directory. Each instrumenter will be required in its own process to avoid interferences through the global object. Errors thrown while evaluating instrumented targets will stop the entire cross testing.

testrumenter instrument target

Bundle

Generate a html page that will apply the instrumenter and the target and evaluate the instrumented code. This is usefull to debug instrumenter on browsers with the debugger statement.

testrumenter instrument.js target.js bundle.html