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

expect-runtime

v0.10.1

Published

expect assertion on the runtime

Downloads

62

Readme

The library to assert javascript code on the runtime.

The name 'expect' was borrowed from Jest. And the syntax of assert is inspired by Jest and Chai.

Motivation

  1. Javascript is a weak type language

Because that Javascript is a weak type language, when we code interace, like function, API, and so on, we often run into unexpected problem because we are giving the interface wrong augments, sometimes it's because we forgot the interace spec, sometimes it's because we made some refactor, and the type of the arguments changed in the chain of the path passing the arguments from one layer of call to other.

  1. TDD

Test driven development let you write code that throw error first, then write more code to correct it. Using runtime assertion let you find why the test failed earlier, at earlier part of code in you program. That helps.

Don't type a lot of console.log(...) to check the state of your program, scrolling the screen to verify the log, use assertion (both in your test code and real code) to let it alert you when something went wrong. TDD let you just focus your attestion on PROBLEMS.

How to test

npm test