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

strict-array-sort

v0.0.4

Published

Check for wrong comparators, returning boolean, in Array.sort

Downloads

1

Readme

strict-array-sort

npm license Build Status dependencies Status devDependencies Status Coverage Status Known Vulnerabilities

The problem

Many developers don't look up documentation quite enough, and sometimes think that comparator function in Array.sort should return boolean and implement sorting like this:

[1,3,2,4,5].sort((a,b)=>a>b);

returns

[ 1, 2, 3, 4, 5 ]

Sometimes it even works if you are lucky. But comparator function should return positive number, negative number or zero, otherwise sorting is broken:

[5, 8, 7, 1, 2, 3, 4, 6, 9, 10, 11, 12, 13].sort((a, b) => a > b)

returns

[ 4, 5, 3, 1, 2, 6, 7, 8, 9, 10, 11, 12, 13 ]

Also, there were changes in sorting in V8, and using booleans in comparators is broken even more than it was before.

[1,3,2,4,5].sort((a,b)=>a>b);

[ 1, 3, 2, 4, 5 ]

Solution

Of cause, you will have to fix your code. But to fix something, you need to find it at first, yeah? And sometimes you have a really large codebase to search in. That's when this module will help you. It has two modes:

Strict mode

All code which returns non numeric values from comparators will start throwing errors. To enable it, just install the module and initialize it like this:

const strictSort = require('strict-array-sort');
strictSort.apply();

Soft mode

If you don't want to throw errors, and want to just write logs, you can do it too:

const strictSort = require('strict-array-sort');
strictSort
  .apply((res, a, b)=>console.log(`Wrong sort result ${res} with args ${a} and ${b} on ${new Error().stack}`));

Warning

This module overrides Array.sort prototype to add check for comparator.

It is pretty dangerous and probably should not be used in production code.