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

@artstesh/it-should

v2.0.1

Published

It should work!.. Shouldn't it? ;)

Downloads

474

Readme

it-should

Overview

The basic set of asserts/expected does not have ready-made solutions for many situations, such as determining the ordering of arrays, comparing objects with conditions, and so on. it-should is designed to make it easier to write assertions for situations like this during code testing.

Consider a small example:

We have a certain service that gives a list of students on request. Among the requirements we have the mandatory sorting of the output list.

// interface Student {name: string, age: number}
describe('student.service', () => {
   it("getAll ordered", () => {
      let students: Student[] = studentService.getAll();
      //
      should().array(students).ordered({by: e => e?.age});
   });
});

If the service fails and returns an unsorted collection, the test will fail, and we will see Elements aren't ordered. in the console.

Of course, it would be possible to prepare the data by leaving only two records in the returned collection and sorting it in reverse order, and compare only these two records in expected... But all these actions, no matter how primitive and simple they were, create quite an impressive amount of work in a real application. It is for such simplifications that this mini-library is created.

Warning

At the moment, the project is at the very beginning of its journey and does not have full-fledged functionality, the number (and, hopefully, the quality) of available functions will increase regularly in the near future.

License

This project is under the MIT license