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

assert-tsn

v1.0.0

Published

Assert functions for Typescript and Javascript.

Downloads

2

Readme

assert-tsn

assertions for typescript and javascript

Installation

npm install assert-tsn --save

Usage

Typescript or JavaScript

All these functions throw exceptions if a false assertion is encountered. In addition if console.error is defined and the Error class supports stack traces, a stack trace will be printed to the console. And if the alert function exists in the global context, then it is called with the message.

The check function:

import assert = require( 'assert' ) ;

assert.check( 2+2===4, "Message zero") ;
assert.check( 2+2===5, "Message one" ) ;

Should throw an exception new Error("Assertion failed: Message one"). The message is optional.

The checkEqual function:

import assert = require( 'assert' ) ;

assert.checkEqual( expected, actual ) ;

Uses === for comparison.

The checkInvariant function:

import assert = require( 'assert' ) ;

...

class Foo {

    private ok() : boolean { ... }
    
    public foo() : void {
        ...
        assert.checkInvariant( ok(), "Corrupted Foo" ) ;
    }
}

Message is optional.

The checkPrecondition function.

import assert = require( 'assert' ) ;

function someFunction( i : number, n : number) : string {
    assert.checkPrecondition( 0 <= i && i < n ) ;
}

The message is optional. The result type is never.

check, checkPrecondition, and checkInvariant are essentially the same, but differ in their intended usage and in their messages.

The failedPrecondition function.

import assert = require( 'assert' ) ;

function someFunction( i : number) : string {
    switch( i ) {
        case -1: return "too small" ;
        case 0 : return "just right" ;
        case +1 : return "too big" ;
        default: return assert.failedPrecondition("out of range") ;
}

The message is optional. The result type is never. Since never is a subtype of all types, the "value" of failedPrecondition can be returned from any function.

The todo function

import assert = require( 'assert' ) ;

function someFunctionWithAResult() : string {
    return assert.todo( "someFunctionWithAResult not yet implemented" ) ; 
}

function someVoidFunction() : void {
    assert.todo( "someVoidFunction not yet implemented" ) ; 
}

The message is optional. The result type is never. Since never is a subtype of all types, the "value" of todo can be returned from any function.

The unreachable function.

import assert = require( 'assert' ) ;

...
    let b : boolean ;
    switch( s ) {
        case "yes": b = true  ;
        case "no" : b = false ;
        default: return assert.unreachable("s has a bad value") ;
}

The message is optional. The result type is never. Since never is a subtype of all types, the "value" of unreachable can be returned from any function.

unreachable, todo and failedPrecondition are essentially all the same but differ in their intended usage and the error messages differ.