to-regex-range - npm Package Compare versions

Comparing version 2.1.0 to 2.1.1

package.json

 {
   "name": "to-regex-range",
-  "description": "Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.87 million test assertions.",
-  "version": "2.1.0",
-  "homepage": "https://github.com/jonschlinkert/to-regex-range",
+  "description": "Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.",
+  "version": "2.1.1",
+  "homepage": "https://github.com/micromatch/to-regex-range",
   "author": "Jon Schlinkert (https://github.com/jonschlinkert)",
-  "repository": "jonschlinkert/to-regex-range",
+  "repository": "micromatch/to-regex-range",
   "bugs": {
-    "url": "https://github.com/jonschlinkert/to-regex-range/issues"
+    "url": "https://github.com/micromatch/to-regex-range/issues"
   },
@@ -78,4 +78,10 @@ "license": "MIT",
       "./examples.js"
+    ],
+    "reflinks": [
+      "0-5",
+      "0-9",
+      "1-5",
+      "1-9"
     ]
   }
 }

README.md

@@ -1,4 +0,4 @@
-# to-regex-range [![NPM version](https://img.shields.io/npm/v/to-regex-range.svg?style=flat)](https://www.npmjs.com/package/to-regex-range) [![NPM monthly downloads](https://img.shields.io/npm/dm/to-regex-range.svg?style=flat)](https://npmjs.org/package/to-regex-range)  [![NPM total downloads](https://img.shields.io/npm/dt/to-regex-range.svg?style=flat)](https://npmjs.org/package/to-regex-range) [![Linux Build Status](https://img.shields.io/travis/jonschlinkert/to-regex-range.svg?style=flat&label=Travis)](https://travis-ci.org/jonschlinkert/to-regex-range)
+# to-regex-range [![NPM version](https://img.shields.io/npm/v/to-regex-range.svg?style=flat)](https://www.npmjs.com/package/to-regex-range) [![NPM monthly downloads](https://img.shields.io/npm/dm/to-regex-range.svg?style=flat)](https://npmjs.org/package/to-regex-range)  [![NPM total downloads](https://img.shields.io/npm/dt/to-regex-range.svg?style=flat)](https://npmjs.org/package/to-regex-range) [![Linux Build Status](https://img.shields.io/travis/micromatch/to-regex-range.svg?style=flat&label=Travis)](https://travis-ci.org/micromatch/to-regex-range)
 
-> Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.87 million test assertions.
+> Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.
 
@@ -66,3 +66,3 @@ ## Install
 
-As of April 22, 2017, this library runs [2,783,483 test assertions](./test/test.js) against generated regex-ranges to provide brute-force verification that results are indeed correct.
+As of April 27, 2017, this library runs [2,783,483 test assertions](./test/test.js) against generated regex-ranges to provide brute-force verification that results are indeed correct.
 
@@ -142,3 +142,3 @@ Tests run in ~870ms on my MacBook Pro, 2.5 GHz Intel Core i7.
 
-**Deafault**: `true`
+**Default**: `true`
 
@@ -166,3 +166,3 @@ This option only applies to **negative zero-padded ranges**. By default, when a negative zero-padded range is defined, the number of leading zeros is relaxed using `-0*`.
 
-In most zero-padding implementations, only a single leading zero is enough to indicate that zero-padding should be applied. Thus, the leading zeros would be "corrected" on the negative range in the example to `-01`, instead of `-001`, to make total length of each string no greater than the length of the largest number in the range.
+In most zero-padding implementations, only a single leading zero is enough to indicate that zero-padding should be applied. Thus, the leading zeros would be "corrected" on the negative range in the example to `-01`, instead of `-001`, to make total length of each string no greater than the length of the largest number in the range (in other words, `-001` is 4 digits, but `100` is only three digits).
 
@@ -177,23 +177,23 @@ If zeros were not relaxed by default, you might expect the resulting regex of the above pattern to match `-001` - given that it's defined that way in the arguments - _but it wouldn't_. It would, however, match `-01`. This gets even more ambiguous with large ranges, like `-01` to `1000000`.
 
-| **Range**                     | **Result**                                                  | **Compile time** |
-| ---                           | ---                                                         | ---              |
-| `toRegexRange('5, 5')`        | `5`                                                         | _25μs_           |
-| `toRegexRange('5, 6')`        | `5\|6`                                                      | _41μs_           |
-| `toRegexRange('29, 51')`      | `29\|[34][0-9]\|5[01]`                                      | _444μs_          |
-| `toRegexRange('31, 877')`     | `3[1-9]\|[4-9][0-9]\|[1-7][0-9]{2}\|8[0-6][0-9]\|87[0-7]`   | _833μs_          |
-| `toRegexRange('111, 555')`    | `11[1-9]\|1[2-9][0-9]\|[2-4][0-9]{2}\|5[0-4][0-9]\|55[0-5]` | _56μs_           |
-| `toRegexRange('-10, 10')`     | `-[1-9]\|-?10\|[0-9]`                                       | _63μs_           |
-| `toRegexRange('-100, -10')`   | `-1[0-9]\|-[2-9][0-9]\|-100`                                | _42μs_           |
-| `toRegexRange('-100, 100')`   | `-[1-9]\|-?[1-9][0-9]\|-?100\|[0-9]`                        | _41μs_           |
-| `toRegexRange('001, 100')`    | `0{2}[1-9]\|0[1-9][0-9]\|100`                               | _134μs_          |
-| `toRegexRange('0010, 1000')`  | `0{2}1[0-9]\|0{2}[2-9][0-9]\|0[1-9][0-9]{2}\|1000`          | _58μs_           |
-| `toRegexRange('1, 2')`        | `1\|2`                                                      | _10μs_           |
-| `toRegexRange('1, 5')`        | `[1-5]`                                                     | _23μs_           |
-| `toRegexRange('1, 10')`       | `[1-9]\|10`                                                 | _21μs_           |
-| `toRegexRange('1, 100')`      | `[1-9]\|[1-9][0-9]\|100`                                    | _23μs_           |
-| `toRegexRange('1, 1000')`     | `[1-9]\|[1-9][0-9]{1,2}\|1000`                              | _50μs_           |
-| `toRegexRange('1, 10000')`    | `[1-9]\|[1-9][0-9]{1,3}\|10000`                             | _132μs_          |
-| `toRegexRange('1, 100000')`   | `[1-9]\|[1-9][0-9]{1,4}\|100000`                            | _42μs_           |
-| `toRegexRange('1, 1000000')`  | `[1-9]\|[1-9][0-9]{1,5}\|1000000`                           | _46μs_           |
-| `toRegexRange('1, 10000000')` | `[1-9]\|[1-9][0-9]{1,6}\|10000000`                          | _60μs_           |
+| **Range** | **Result** | **Compile time** | 
+| --- | --- | --- |
+| `toRegexRange('5, 5')` | `5` | _33μs_ |
+| `toRegexRange('5, 6')` | `5\|6` | _53μs_ |
+| `toRegexRange('29, 51')` | `29\|[34][0-9]\|5[01]` | _699μs_ |
+| `toRegexRange('31, 877')` | `3[1-9]\|[4-9][0-9]\|[1-7][0-9]{2}\|8[0-6][0-9]\|87[0-7]` | _711μs_ |
+| `toRegexRange('111, 555')` | `11[1-9]\|1[2-9][0-9]\|[2-4][0-9]{2}\|5[0-4][0-9]\|55[0-5]` | _62μs_ |
+| `toRegexRange('-10, 10')` | `-[1-9]\|-?10\|[0-9]` | _74μs_ |
+| `toRegexRange('-100, -10')` | `-1[0-9]\|-[2-9][0-9]\|-100` | _49μs_ |
+| `toRegexRange('-100, 100')` | `-[1-9]\|-?[1-9][0-9]\|-?100\|[0-9]` | _45μs_ |
+| `toRegexRange('001, 100')` | `0{2}[1-9]\|0[1-9][0-9]\|100` | _158μs_ |
+| `toRegexRange('0010, 1000')` | `0{2}1[0-9]\|0{2}[2-9][0-9]\|0[1-9][0-9]{2}\|1000` | _61μs_ |
+| `toRegexRange('1, 2')` | `1\|2` | _10μs_ |
+| `toRegexRange('1, 5')` | `[1-5]` | _24μs_ |
+| `toRegexRange('1, 10')` | `[1-9]\|10` | _23μs_ |
+| `toRegexRange('1, 100')` | `[1-9]\|[1-9][0-9]\|100` | _30μs_ |
+| `toRegexRange('1, 1000')` | `[1-9]\|[1-9][0-9]{1,2}\|1000` | _52μs_ |
+| `toRegexRange('1, 10000')` | `[1-9]\|[1-9][0-9]{1,3}\|10000` | _47μs_ |
+| `toRegexRange('1, 100000')` | `[1-9]\|[1-9][0-9]{1,4}\|100000` | _44μs_ |
+| `toRegexRange('1, 1000000')` | `[1-9]\|[1-9][0-9]{1,5}\|1000000` | _49μs_ |
+| `toRegexRange('1, 10000000')` | `[1-9]\|[1-9][0-9]{1,6}\|10000000` | _63μs_ |
 
@@ -285,2 +285,2 @@ ## Heads up!
 
-_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.5.0, on April 22, 2017._
+_This file was generated by [verb-generate-readme](https://github.com/verbose/verb-generate-readme), v0.6.0, on April 27, 2017._

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

Worsened metrics

Total package byte prevSize

20259

decreased by-4.24%

No dependency changes