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 🙏

© 2025 – Pkg Stats / Ryan Hefner

treest

v0.2.3

Published

Real-automatic testing.

Downloads

57

Readme

treest

Real-automatic testing.

NPM version Build Status Dependency Status Coverage percentage experimental

Concept

Look at folder __fixtures__. We have 4 modules: module1, module2, module3 and ClassA. Every module has own exports, like, functions or classes.

We want to have the unit tests for all of it.

BUT, we don't want to write it. Ok, Treest can do this instead of us!

Just call any function or method of class, which call some another function and Treest will be log (save to files) all calls, sub-calls and sub-sub-calls (so, Treest is TREE's teSTing).

Next time, when we start an executing of this function, Treest will compare the old and the new result (with same arguments) and throw error, if they will be different.

Restrictions

Treest logged the arguments and results of all functions, so, it imposes some restrictions. Shortly, Treest can work only with serializable objects.

Treest supports all primitive js-types: boolean, plain-object, array, string, number, null, undefined.

Treest supports object, created by class or prototype. For passing by reference, Treest used a method toJSON of class for saving a state of object (really, Treest just used JSON.stringify).

Treest don't support the anonymouses functions, i know, it is big problem, but you can use property of class, like this:

class A {
    public method1 = () => {
        // this.anotherMethod(); this exists in context
    };
}
function b(func: ()=>void){
    func();
}
const a = new A();
b(a.method1);

Install

npm install treest --save

or 

yarn add treest

Usage

import { Treest } from "treest";

const treest = new Treest();
const module1 = treest.require("./module1"); // require js-module with export-function `hello`
module1.hello("world"); // call function, log all sub-calls and write it to __treest__/%modulename%.json
//look at folder __treest__

API

interface ITreestConfig {
    mode?: string;
    mocks?: { [index: string]: () => any };
    ignoreMockModules?: string[];
    reporter?: typeof console;
    knownClasses?: Array<{
        class: any;
        name: string;
    }>;
    realRequire?: typeof require;
}

Test

npm install
npm test