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

@efekos/es-test

v1.0.7

Published

Test runner for ES Modules

Downloads

13

Readme

es-test v1.0.7

Simple test runner to use in ESM modules.

After trying to use jest with an esm module for so long i just gave up and made this module. This module will scan for every .test.js or .spec.js file in current workspace and try running them. You can limit scanning into one directory by passing in the dir name like this:

  • C:\myapp> estest - Scans C:\myapp
  • C:\myapp> estest dist - Scans C:\myapp\dist

Usage

  • npm i -D @efekos/es-test
  • Create a test script to run estest: "estest" (Also create pretest to compile if you use TypeScript)
  • Write some tests
  • Run npm test

Writing tests

import {describe,it,inst} from '@efekos/es-test/bin/testRunner.js' // You excplicitly have to import from testRunner.js i have no idea why
import {expect} from 'chai' // or any other assertion module

describe('9 + 10',()=>{ // create a suite with describe

    it('should be 21',()=>{ // create a test with it

        expect(9+10).to.be.equal(21);

    });
});

function isNumber(s){
    return /[+-]?\d+(\.\d+)?/.test(s);
}

describe('isNumber function',()=>{

    it('should match all the numbers',()=>{

        inst(()=>{ // Create different cases with inst
            expect(isNumber('5')).to.be.equal(true)
        });
        
        inst(()=>{
            expect(isNumber('455.34')).to.be.equal(true)
        });
        
        inst(()=>{
            expect(isNumber('-145')).to.be.equal(true)
        });
        
        inst(()=>{
            expect(isNumber('-3465.0000000003')).to.be.equal(true)
        });
        
        inst(()=>{
            expect(isNumber('-.3495')).to.be.equal(true)
        });
        
        inst(()=>{
            expect(isNumber('+.25')).to.be.equal(true)
        });

    },true /*this true makes this test a cased test*/);

});

Handling errors

import {onError} from '@efekos/es-test/bin/testRunner.js'

onError('CustomError',(err)=>{ // Handle custom error types
    return {
        passed:false,
        expected:err.exp,
        actual:err.act,
        formatMode:'none' // 'str' will make every difference in actual value look red instead of making it completely red in summary
    }
})