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

typed-nodejs-assert

v1.1.0

Published

improved type definitions for assertions in the nodeJS assert API

Downloads

72

Readme

typed nodejs assert

various fixes for nodeJS assertions in typescript.

npm

what it do

this packages fixes the following issues:

  • the typescript definitions for the default assertion library in nodeJS do not properly check the types of expected/actual values, leading to assertion errors that could easily be caught by the compiler.

    for example. in the current type definitions, the following error would not occur:

    type Foo = {
        bar: number
    }
    const foo: Foo = {
        bar: 1
    }
    //@ts-expect-error TS2345: Argument of type '{}' is not assignable to parameter of type 'Foo'. Property 'bar' is missing in type '{}' but required in type 'Foo'
    assert.deepStrictEqual(foo, {})
  • power-assert can only be imported using UMD syntax (ie. const assert = require('power-assert')), meaning it's treated as any by the compiler in many cases

how to use

normally

import assert from 'typed-nodejs-assert'

with power-assert

due to the fact that power-assert usually has to be imported using UMD syntax, you have to import it as such and give it the PowerAsssert type from this package.

import { PowerAssert } from 'typed-nodejs-assert'
const assert: PowerAssert = require('power-assert')

IMPORTANT: you have to explicitly specify the type as shown above. the following will not work:

const assert = require('power-assert') as PowerAssert

see this issue for more info