Changelog

5.0.0

💥 BREAKING CHANGES

• Minimum supported Node version is v14.18; we’re dropping v12 support

4.1.0

✨ Features

• export types (11b5fb9)

4.0.0

✨ Features

• migrate to ES Modules (8c9d95d)

💥 BREAKING CHANGES

• programs now are in ES Modules and won’t work with Common JS require()

3.1.0

✨ Features

• config file based major bump blacklisting (e15f9bb)

3.0.15

⏪ Reverts

• Revert “chore: setup refresh” (23cf206)

3.0.1

🔧 Fixed

• add testStats to npmignore (f3c84e9)

3.0.0

✨ Features

• rewrite in TS, start using named exports (cbaa3b3)

💥 BREAKING CHANGES

• previously: import sortBySubarray from … — now import { sortByCol } from …

2.13.0

Accidental version bump during migration to SourceHut. Sorry about that.

2.12.0

✨ Features

• remove all dependencies (1536b15)

2.11.0

✨ Features

• Add perf measurement, recording and historical comparison (eb6fb04)

2.10.0

• Various documentation and setup tweaks after we migrated to monorepo
• Setup refresh: updated dependencies and all config files using automated tools

2.4.0

✨ Features

• cater null values too (38fa255)
• rippling sort from arbitrary axis column (38d850f)

2.3.0

• Updated all dependencies and restored AVA linting, added licence to the top of each built file

2.2.0

• Updated all dependencies and restored coverage reporting both in terminal and sending to coveralls

2.1.0

GitHub sold us out. In the meantime, we:

• Migrated to BitBucket (to host repo + perform CI) and Codacy (for code quality audit)
• Dropped BitHound (RIP) and Travis
• Removed package-lock

2.0.0

Complete rewrite.

• Now it’s sorting by “rippling” from the chosen column (default 0). Always, first goes value to the first value left, then, first value to the right. After that, “ripple” is expanded and the next value outside to the left is checked, then, one to the right. This is repeated until there are no values to compare both on the left and on the right.

The previous versions’ unit tests will pass mainly, this “rippling” sort first of all concerns the cases where the sorting “axis” is in the middle of sub-arrays and we want the existent values to “clump” around the axis, raising to the top.

For example, the 1 should be on top of null if sorting “axis” is third column where 7‘s are:

...
    null      1       7    null null
    null   null       7    null null
…

• Plus, first time ever, I pointed unit tests at ES Modules build.
• Plus, first time ever, I turned off Babel for ES Modules build. In turn, first time ever the code coverage appears correct. No more uncovered functions that Babel added!

1.0.0

• Public release