globrex

Install

npm install globrex --save

Core Features

• extended globbing: transform advance ExtGlob features
• simple: no dependencies
• paths: split paths into multiple RegExp segments

Usage

const globrex = require('globrex');

const result = globrex('p*uck')
// => { regex: /^p.*uck$/, string: '^p.*uck
API
globrex(glob, options)
Type: function

Returns: Object
Transform globs intp regular expressions.
Returns object with the following properties:
regex
Type: RegExp
JavaScript RegExp instance.
Note: Read more about how to use RegExp on MDN.

path
This property only exists if the option filepath is true.
Note: filepath is false by default

path.segments
Type: Array
Array of RegExp instances seperated by /. 
This can be usable when working with file paths or urls. 
Example array could be:
[ /^foo$/, /^bar$/, /^([^\/]*)$/, '^baz\\.(md|js|txt)
path.regex
Type: RegExp
JavaScript RegExp instance build for testign against paths.
The regex have different path seperators depending on host OS.
glob
Type: String
Glob string to transform.
options.extended
Type: Boolean

Default: false
Enable all advanced features from extglob.
Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.
Note: Interprets [a-d] as [abcd]. To match a literal -, include it as first or last character.

options.globstar
Type: Boolean

Default: false
When globstar is false globs like '/foo/*' are transformed to the following
'^\/foo\/.* which will match any string beginning with '/foo/'.

When the globstar option is true, the same '/foo/*' glob is transformed to
'^\/foo\/[^/]* which will match any string beginning with '/foo/' that does not have a '/' to the right of it. '/foo/*' will match: '/foo/bar', '/foo/bar.txt' but not '/foo/bar/baz' or '/foo/bar/baz.txt'.

Note: When globstar is true, '/foo/**' is equivelant to '/foo/*' when globstar is false.

options.strict
Type: Boolean

Default: false
Be forgiving about mutiple slashes, like /// and make everything after the first / optional. This is how bash glob works.
options.flags
Type: String

Default: ''
RegExp flags (e.g. 'i' ) to pass to the RegExp constructor.
options.filepath
Type: Boolean

Default: false
Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like /foo/bar/hello.js or URLs.
When true the returned object will have an additional path object.

segment: Array containing a RegExp object for each path segment.
regex: OS specific file path RegExp. Path seperator used is based on the operating system.
globstar: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions
Though windows uses either / or \ as its path separator, only /
characters are used by this glob implementation.  You must use
forward-slashes only in glob expressions. Back-slashes will always
be interpreted as escape characters, not path separators.

References
Learn more about advanced globbing here

mywiki.wooledge.org/glob
linuxjournal

License
MIT  Terkel Gjervig
, segments: [ /^p.*uck$/ ] }

result.regex.test('pluck'); // true

API
globrex(glob, options)
Type: __INLINE_CODE_2__

Returns: __INLINE_CODE_3__
Transform globs intp regular expressions.
Returns object with the following properties:
regex
Type: __INLINE_CODE_4__
JavaScript __INLINE_CODE_5__ instance.
Note: Read more about how to use RegExp on MDN.

path
This property only exists if the option __INLINE_CODE_6__ is true.
Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments
Type: __INLINE_CODE_9__
Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. 
This can be usable when working with file paths or urls. 
Example array could be:
__CODE_BLOCK_2__
path.regex
Type: __INLINE_CODE_12__
JavaScript __INLINE_CODE_13__ instance build for testign against paths.
The regex have different path seperators depending on host OS.
glob
Type: __INLINE_CODE_14__
Glob string to transform.
options.extended
Type: __INLINE_CODE_15__

Default: __INLINE_CODE_16__
Enable all advanced features from __INLINE_CODE_17__.
Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.
Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar
Type: __INLINE_CODE_21__

Default: __INLINE_CODE_22__
When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following
__INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.
When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to
__INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.
Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict
Type: __INLINE_CODE_41__

Default: __INLINE_CODE_42__
Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.
options.flags
Type: __INLINE_CODE_45__

Default: __INLINE_CODE_46__
RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.
options.filepath
Type: __INLINE_CODE_48__

Default: __INLINE_CODE_49__
Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.
When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

__INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
__INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
__INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions
Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__
characters are used by this glob implementation.  You must use
forward-slashes only in glob expressions. Back-slashes will always
be interpreted as escape characters, not path separators.

References
Learn more about advanced globbing here

mywiki.wooledge.org/glob
linuxjournal

License
MIT  Terkel Gjervig
 ]

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

]

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

]

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

]

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig

, segments: [ /^p.*uck$/ ] } result.regex.test('pluck'); // true

API

globrex(glob, options)

Type: __INLINE_CODE_2__
Returns: __INLINE_CODE_3__

Transform globs intp regular expressions. Returns object with the following properties:

regex

Type: __INLINE_CODE_4__

JavaScript __INLINE_CODE_5__ instance.

Note: Read more about how to use RegExp on MDN.

path

This property only exists if the option __INLINE_CODE_6__ is true.

Note: __INLINE_CODE_7__ is __INLINE_CODE_8__ by default

path.segments

Type: __INLINE_CODE_9__

Array of __INLINE_CODE_10__ instances seperated by __INLINE_CODE_11__. This can be usable when working with file paths or urls.

Example array could be:

__CODE_BLOCK_2__

path.regex

Type: __INLINE_CODE_12__

JavaScript __INLINE_CODE_13__ instance build for testign against paths. The regex have different path seperators depending on host OS.

glob

Type: __INLINE_CODE_14__

Glob string to transform.

options.extended

Type: __INLINE_CODE_15__
Default: __INLINE_CODE_16__

Enable all advanced features from __INLINE_CODE_17__.

Matching so called "extended" globs pattern like single character matching, matching ranges of characters, group matching, etc.

Note: Interprets __INLINE_CODE_18__ as __INLINE_CODE_19__. To match a literal __INLINE_CODE_20__, include it as first or last character.

options.globstar

Type: __INLINE_CODE_21__
Default: __INLINE_CODE_22__

When globstar is __INLINE_CODE_23__ globs like __INLINE_CODE_24__ are transformed to the following __INLINE_CODE_25__ which will match any string beginning with __INLINE_CODE_26__.

When the globstar option is __INLINE_CODE_27__, the same __INLINE_CODE_28__ glob is transformed to __INLINE_CODE_29__ which will match any string beginning with __INLINE_CODE_30__ that does not have a __INLINE_CODE_31__ to the right of it. __INLINE_CODE_32__ will match: __INLINE_CODE_33__, __INLINE_CODE_34__ but not __INLINE_CODE_35__ or __INLINE_CODE_36__.

Note: When globstar is __INLINE_CODE_37__, __INLINE_CODE_38__ is equivelant to __INLINE_CODE_39__ when globstar is __INLINE_CODE_40__.

options.strict

Type: __INLINE_CODE_41__
Default: __INLINE_CODE_42__

Be forgiving about mutiple slashes, like __INLINE_CODE_43__ and make everything after the first __INLINE_CODE_44__ optional. This is how bash glob works.

options.flags

Type: __INLINE_CODE_45__
Default: __INLINE_CODE_46__

RegExp flags (e.g. __INLINE_CODE_47__ ) to pass to the RegExp constructor.

options.filepath

Type: __INLINE_CODE_48__
Default: __INLINE_CODE_49__

Parse input strings as it was a file path for special path related features. This feature only makes sense if the input is a POSIX path like __INLINE_CODE_50__ or URLs.

When __INLINE_CODE_51__ the returned object will have an additional __INLINE_CODE_52__ object.

• __INLINE_CODE_53__: Array containing a __INLINE_CODE_54__ object for each path segment.
• __INLINE_CODE_55__: OS specific file path __INLINE_CODE_56__. Path seperator used is based on the operating system.
• __INLINE_CODE_57__: Regex string used to test for globstars.

Note: Please only use forward-slashes in file path glob expressions Though windows uses either __INLINE_CODE_58__ or __INLINE_CODE_59__ as its path separator, only __INLINE_CODE_60__ characters are used by this glob implementation. You must use forward-slashes only in glob expressions. Back-slashes will always be interpreted as escape characters, not path separators.

References

Learn more about advanced globbing here

• mywiki.wooledge.org/glob
• linuxjournal

License

MIT Terkel Gjervig