to-regex-range

to-regex-range

Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your and support.

Install

Install with npm:

$ npm install --save to-regex-range

const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));

Usage

Add this library to your javascript application with the following line of code

const toRegexRange = require('to-regex-range');

The main export is a function that takes two integers: the min value and max value (formatted as strings or numbers).

const source = toRegexRange('15', '95');
//=> 1[5-9]|[2-8][0-9]|9[0-5]

const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
);
console.log(regex.test('14')); //=> false
console.log(regex.test('50')); //=> true
console.log(regex.test('94')); //=> true
console.log(regex.test('96')); //=> false

Options

options.capture

Type: boolean

Deafault: undefined

Wrap the returned value in parentheses when there is more than one regex condition. Useful when you're dynamically generating ranges.

console.log(toRegexRange('-10', '10'));
//=> -[1-9]|-?10|[0-9]

console.log(toRegexRange('-10', '10', { capture: true }));
//=> (-[1-9]|-?10|[0-9])

options.shorthand

Type: boolean

Deafault: undefined

Use the regex shorthand for [0-9]:

console.log(toRegexRange('0', '999999'));
//=> [0-9]|[1-9][0-9]{1,5}

console.log(toRegexRange('0', '999999', { shorthand: true }));
//=> \d|[1-9]\d{1,5}

options.relaxZeros

Type: boolean

Default: true

This option relaxes matching for leading zeros when when ranges are zero-padded.

const source = toRegexRange('-0010', '0010');
const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
const source = toRegexRange('15', '95');
//=> 1[5-9]|[2-8][0-9]|9[0-5]

const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
);
console.log(regex.test('14')); //=> false
console.log(regex.test('50')); //=> true
console.log(regex.test('94')); //=> true
console.log(regex.test('96')); //=> false
Options
options.capture
Type: __INLINE_CODE_28__
Deafault: __INLINE_CODE_29__
Wrap the returned value in parentheses when there is more than one regex condition. Useful when you're dynamically generating ranges.
console.log(toRegexRange('-10', '10'));
//=> -[1-9]|-?10|[0-9]

console.log(toRegexRange('-10', '10', { capture: true }));
//=> (-[1-9]|-?10|[0-9])
options.shorthand
Type: __INLINE_CODE_30__
Deafault: __INLINE_CODE_31__
Use the regex shorthand for __INLINE_CODE_32__:
console.log(toRegexRange('0', '999999'));
//=> [0-9]|[1-9][0-9]{1,5}

console.log(toRegexRange('0', '999999', { shorthand: true }));
//=> \d|[1-9]\d{1,5}
options.relaxZeros
Type: __INLINE_CODE_33__
Default: __INLINE_CODE_34__
This option relaxes matching for leading zeros when when ranges are zero-padded.
);
console.log(regex.test('-10')); //=> true
console.log(regex.test('-010')); //=> true
console.log(regex.test('-0010')); //=> true
console.log(regex.test('10')); //=> true
console.log(regex.test('010')); //=> true
console.log(regex.test('0010')); //=> true

When relaxZeros is false, matching is strict:

const source = toRegexRange('-0010', '0010', { relaxZeros: false });
const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
const source = toRegexRange('15', '95');
//=> 1[5-9]|[2-8][0-9]|9[0-5]

const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
);
console.log(regex.test('14')); //=> false
console.log(regex.test('50')); //=> true
console.log(regex.test('94')); //=> true
console.log(regex.test('96')); //=> false
Options
options.capture
Type: __INLINE_CODE_28__
Deafault: __INLINE_CODE_29__
Wrap the returned value in parentheses when there is more than one regex condition. Useful when you're dynamically generating ranges.
console.log(toRegexRange('-10', '10'));
//=> -[1-9]|-?10|[0-9]

console.log(toRegexRange('-10', '10', { capture: true }));
//=> (-[1-9]|-?10|[0-9])
options.shorthand
Type: __INLINE_CODE_30__
Deafault: __INLINE_CODE_31__
Use the regex shorthand for __INLINE_CODE_32__:
console.log(toRegexRange('0', '999999'));
//=> [0-9]|[1-9][0-9]{1,5}

console.log(toRegexRange('0', '999999', { shorthand: true }));
//=> \d|[1-9]\d{1,5}
options.relaxZeros
Type: __INLINE_CODE_33__
Default: __INLINE_CODE_34__
This option relaxes matching for leading zeros when when ranges are zero-padded.
const source = toRegexRange('-0010', '0010');
const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
const source = toRegexRange('15', '95');
//=> 1[5-9]|[2-8][0-9]|9[0-5]

const regex = new RegExp(`^${source}
to-regex-range     
Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your  and support.
Install
Install with npm:
$ npm install --save to-regex-range

What does this do?

This libary generates the __INLINE_CODE_0__ string to be passed to __INLINE_CODE_1__ for matching a range of numbers.
Example
const toRegexRange = require('to-regex-range');
const regex = new RegExp(toRegexRange('15', '95'));
A string is returned so that you can do whatever you need with it before passing it to __INLINE_CODE_2__ (like adding __INLINE_CODE_3__ or __INLINE_CODE_4__ boundaries, defining flags, or combining it another string).


Why use this library?

Convenience
Creating regular expressions for matching numbers gets deceptively complicated pretty fast.
For example, let's say you need a validation regex for matching part of a user-id, postal code, social security number, tax id, etc:

regex for matching __INLINE_CODE_5__ => __INLINE_CODE_6__ (easy enough)
regex for matching __INLINE_CODE_7__ through __INLINE_CODE_8__ => __INLINE_CODE_9__ (not bad...)
regex for matching __INLINE_CODE_10__ or __INLINE_CODE_11__ => __INLINE_CODE_12__ (still easy...)
regex for matching __INLINE_CODE_13__ through __INLINE_CODE_14__ => __INLINE_CODE_15__ (uh-oh...)
regex for matching __INLINE_CODE_16__ through __INLINE_CODE_17__ => __INLINE_CODE_18__ (no prob, I can do this...)
regex for matching __INLINE_CODE_19__ through __INLINE_CODE_20__ => __INLINE_CODE_21__ (maybe not...)
regex for matching __INLINE_CODE_22__ through __INLINE_CODE_23__ => __INLINE_CODE_24__ (okay, I get the point!)

The numbers are contrived, but they're also really basic. In the real world you might need to generate a regex on-the-fly for validation.
Learn more
If you're interested in learning more about character classes and other regex features, I personally have always found regular-expressions.info to be pretty useful.
Heavily tested
As of April 07, 2019, this library runs >1m test assertions against generated regex-ranges to provide brute-force verification that results are correct.
Tests run in ~280ms on my MacBook Pro, 2.5 GHz Intel Core i7.
Optimized
Generated regular expressions are optimized:

duplicate sequences and character classes are reduced using quantifiers
smart enough to use __INLINE_CODE_25__ conditionals when number(s) or range(s) can be positive or negative
uses fragment caching to avoid processing the same exact string more than once


Usage
Add this library to your javascript application with the following line of code
const toRegexRange = require('to-regex-range');
The main export is a function that takes two integers: the __INLINE_CODE_26__ value and __INLINE_CODE_27__ value (formatted as strings or numbers).
);
console.log(regex.test('14')); //=> false
console.log(regex.test('50')); //=> true
console.log(regex.test('94')); //=> true
console.log(regex.test('96')); //=> false
Options
options.capture
Type: __INLINE_CODE_28__
Deafault: __INLINE_CODE_29__
Wrap the returned value in parentheses when there is more than one regex condition. Useful when you're dynamically generating ranges.
console.log(toRegexRange('-10', '10'));
//=> -[1-9]|-?10|[0-9]

console.log(toRegexRange('-10', '10', { capture: true }));
//=> (-[1-9]|-?10|[0-9])
options.shorthand
Type: __INLINE_CODE_30__
Deafault: __INLINE_CODE_31__
Use the regex shorthand for __INLINE_CODE_32__:
console.log(toRegexRange('0', '999999'));
//=> [0-9]|[1-9][0-9]{1,5}

console.log(toRegexRange('0', '999999', { shorthand: true }));
//=> \d|[1-9]\d{1,5}
options.relaxZeros
Type: __INLINE_CODE_33__
Default: __INLINE_CODE_34__
This option relaxes matching for leading zeros when when ranges are zero-padded.
);
console.log(regex.test('-10')); //=> true
console.log(regex.test('-010')); //=> true
console.log(regex.test('-0010')); //=> true
console.log(regex.test('10')); //=> true
console.log(regex.test('010')); //=> true
console.log(regex.test('0010')); //=> true
When __INLINE_CODE_35__ is false, matching is strict:
);
console.log(regex.test('-10')); //=> false
console.log(regex.test('-010')); //=> false
console.log(regex.test('-0010')); //=> true
console.log(regex.test('10')); //=> false
console.log(regex.test('010')); //=> false
console.log(regex.test('0010')); //=> true

Examples

Heads up!

Order of arguments

When the min is larger than the max, values will be flipped to create a valid range:

toRegexRange('51', '29');

Is effectively flipped to:

toRegexRange('29', '51');
//=> 29|[3-4][0-9]|5[0-1]

Steps / increments

This library does not support steps (increments). A pr to add support would be welcome.

History

v2.0.0 - 2017-04-21

New features

Adds support for zero-padding!

v1.0.0

Optimizations

Repeating ranges are now grouped using quantifiers. rocessing time is roughly the same, but the generated regex is much smaller, which should result in faster matching.

Attribution

Inspired by the python library range-regex.

About

$ npm install && npm test

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Related projects

You might also be interested in these projects:

• expand-range: Fast, bash-like range expansion. Expand a range of numbers or letters, uppercase or lowercase. Used… more | homepage
• fill-range: Fill in a range of numbers or letters, optionally passing an increment or step to… more | homepage
• micromatch: Glob matching for javascript/node.js. A drop-in replacement and faster alternative to minimatch and multimatch. | homepage
• repeat-element: Create an array by repeating the given value n times. | homepage
• repeat-string: Repeat the given string n times. Fastest implementation for repeating a string. | homepage

Contributors

Author

Jon Schlinkert

• GitHub Profile
• Twitter Profile
• LinkedIn Profile

Please consider supporting me on Patreon, or start your own Patreon page!

License

Copyright 2019, Jon Schlinkert. Released under the MIT License.

This file was generated by verb-generate-readme, v0.8.0, on April 07, 2019.