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 🙏

© 2026 – Pkg Stats / Ryan Hefner

rinuts

v0.0.3

Published

A service which exposes tests through a RESTful api and allows for querying and running them, using http requests

Readme

rinuts

A service which exposes tests through a RESTful api. Allows for remote querying and running tests on the service, by using http requests", as well as retrieving a detailed run information

built on node and express

Installation

Install with [npm](http://github.com/isaacs/npm):

    $ npm install rinuts

Usage

Starting the service:

var path = require('path'),
    rinuts = require('rinuts'),
    someDriver = require('rinuts-someDriver'),
    service;
    
    // what ever api the driver has to load tests
    someDriver.addTests(*TESTS*);
            
    service = new rinuts(someDriver);
    service.listen(3333);

Service API:

* *ctor*  (driver, context)
    Constructor. Loads a driver which implementes 'enumTests' and 'runTest'.
    [Argument] driver - The driver        
	[Argument] context - (optional) An object being the context of each test run.         

HTTP exposed API:

*	GET /tests : JSON response with a list of the tests exposed. Each test includes it's unique name and a POST URL which can be used to execute it. The list structure is as follows:
        {
            "*testName*": {
                "name": "*testName*",                    
                "url":"/tests/*testName*"
                }
            ...
        }

*	GET /tests/:testName : Returns an individual entry from the list above. has the form of:
		{
			"name": "*testName*",				
			"url": "/tests/*testName*"}

*	POST /tests/:testName : Executes the individual test and returns the test run summary, in the following structure (can be expanded by the driver):            
        {
            "name": *testName*,                
            "state": *true|false*                
        }
		
	Adding context to the request(Optional):		
		HTTP-Headers: "Content-Type: application/json"
		HTTP-Body: {"context": *whatEver*}" - a JSON notated object
	
	note - added context will override context supplied to the *ctor* of rinuts.

Driver interface:

Drivers for rinuts should export the following methods inorder to enable 'rinuts' to 
enumarate the driver's tests as a reponse for 'GET' request and to run a speicific test per 'POST' request:
 
 *  'enumTests' (callback): applies *callback* on an array containing the tests to be exposed. each array element has the form:
        {
            name: *the name of the test*,
            identifier: *the unique identifier of the test. will be appended to the test url in the get reponse, e.g, \tests\testoddnumbers*
        }
 *  'runTest' (identifier, callback, context) : runs the test matching 'identifier', with 'context' if supplied in the in the POST request,
        and applies callback on the testresult.