ml-array-xy-max-y - npm Package Compare versions

Comparing version 0.2.7 to 1.0.0

CHANGELOG.md

@@ -6,2 +6,18 @@ # Change Log
 
+# [1.0.0](https://github.com/mljs/array-xy/compare/ml-array-xy-max-y@0.2.7...ml-array-xy-max-y@1.0.0) (2019-06-29)
+
+
+### chore
+
+* update dependencies and remove support  for Node.js 6 ([dc23f9c](https://github.com/mljs/array-xy/commit/dc23f9c))
+
+
+### BREAKING CHANGES
+
+* Node.js 6 is no longer supported
+
+
+
+
+
 ## [0.2.7](https://github.com/mljs/array-xy/compare/ml-array-xy-max-y@0.2.6...ml-array-xy-max-y@0.2.7) (2019-05-03)
@@ -8,0 +24,0 @@

lib/index.js

@@ -58,5 +58,5 @@ 'use strict';
   if (reverse) {
-    index = binarySearch(x, value, numSort.desc);
+    index = binarySearch(x, value, numSort.descending);
   } else {
-    index = binarySearch(x, value, numSort.asc);
+    index = binarySearch(x, value, numSort.ascending);
   }
@@ -63,0 +63,0 @@

package.json

 {
   "name": "ml-array-xy-max-y",
-  "version": "0.2.7",
+  "version": "1.0.0",
   "description": "Find the maximum ordinate value in a range of abscissas of a {x:[], y:[]}",
@@ -23,6 +23,6 @@ "main": "lib/index.js",
   "dependencies": {
-    "binary-search": "^1.3.2",
-    "num-sort": "^1.0.0"
+    "binary-search": "^1.3.5",
+    "num-sort": "^2.0.0"
   },
   "gitHead": "1321c2b63d8d201d6242bdcbfdb7b7bdfc0e719a"
 }

src/index.js

 import binarySearch from 'binary-search';
-import { asc, desc } from 'num-sort';
+import { ascending, descending } from 'num-sort';
 
@@ -54,5 +54,5 @@ /**
   if (reverse) {
-    index = binarySearch(x, value, desc);
+    index = binarySearch(x, value, descending);
   } else {
-    index = binarySearch(x, value, asc);
+    index = binarySearch(x, value, ascending);
   }
@@ -59,0 +59,0 @@

New alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Fixed alerts

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

9739

3.67%

Number of low quality alerts

1

-50%

Worsened metrics

Number of medium supply chain risk alerts

1

Infinity%

Dependency changes

• + Added

  num-sort@2.1.0
  (transitive)

• - Removed

  num-sort@1.0.0
  (transitive)

• - Removed

  number-is-nan@1.0.1
  (transitive)

• Updated

  binary-search@^1.3.5

• Updated

  num-sort@^2.0.0