Package Exports
- regex-filename-posix
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (regex-filename-posix) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Split Filename
Regular expression to split a POSIX filename.
Installation
$ npm install regex-filename-posix
Usage
var re = require( 'regex-filename-posix' );
re
Regular expression to split a POSIX filename.
var parts = re.exec( '/foo/bar/index.js' );
/*
[
'/foo/bar/index.js', // input value
'/', // root
'foo/bar/', // dirname
'index.js', // basename
'.js' // extname
]
*/
Notes
When executed against dotfile filenames (e.g.,
.gitignore
), the regular expression does not capture the basename as a filename extension.var parts = re.exec( '.bash_profile' ); /* [ '.bash_profile', '', '', '.bash_profile', '' ] */ parts = re.exec( '.travis.yml' ); /* [ '.travis.yml', '', '', '.travis.yml', '.yml' ] */
Examples
var re = require( 'regex-filename-posix' );
var parts;
parts = re.exec( 'index.js' );
/*
[
'index.js',
'',
'',
'index.js',
'.js'
]
*/
parts = re.exec( '/foo/bar/home.html' );
/*
[
'/foo/bar/home.html',
'/',
'foo/bar/',
'home.html',
'.html'
]
*/
parts = re.exec( 'foo/file.pdf' );
/*
[
'foo/file.pdf',
'',
'foo/',
'file.pdf',
'.pdf'
]
*/
parts = re.exec( 'beep/boop.' );
/*
[
'beep/boop.',
'',
'beep/',
'boop.',
'.'
]
*/
parts = re.exec( '' );
/*
[
'',
'',
'',
'',
''
]
*/
parts = re.exec( '/foo/bar/file' );
/*
[
'/foo/bar/file',
'/',
'foo/bar/',
'file',
''
]
*/
parts = re.exec( '/foo/bar/.gitignore' );
/*
[
'/foo/bar/.gitignore',
'/',
'foo/bar/',
'.gitignore',
''
]
*/
To run the example code from the top-level application directory,
$ node ./examples/index.js
Tests
Unit
Unit tests use the Mocha test framework with Chai assertions. To run the tests, execute the following command in the top-level application directory:
$ make test
All new feature development should have corresponding unit tests to validate correct functionality.
Test Coverage
This repository uses Istanbul as its code coverage tool. To generate a test coverage report, execute the following command in the top-level application directory:
$ make test-cov
Istanbul creates a ./reports/coverage
directory. To access an HTML version of the report,
$ make view-cov
License
Copyright
Copyright © 2015. Athan Reines.