We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
5.0 KiB
normalize-path
Normalize file path slashes to be unix-like forward slashes. Also condenses repeat slashes to a single slash and removes and trailing slashes unless disabled.
Install
Install with npm:
$ npm install --save normalize-path
Usage
var normalize = require('normalize-path');
normalize('\\foo\\bar\\baz\\');
//=> '/foo/bar/baz'
normalize('./foo/bar/baz/');
//=> './foo/bar/baz'
Pass false
as the last argument to keep trailing slashes:
normalize('./foo/bar/baz/', false);
//=> './foo/bar/baz/'
normalize('foo\\bar\\baz\\', false);
//=> 'foo/bar/baz/'
About
Related projects
- contains-path: Return true if a file path contains the given path. | homepage
- ends-with: Returns
true
if the givenstring
orarray
ends withsuffix
using strict equality for… more | homepage - is-absolute: Polyfill for node.js
path.isAbolute
. Returns true if a file path is absolute. | homepage - is-relative: Returns
true
if the path appears to be relative. | homepage - parse-filepath: Pollyfill for node.js
path.parse
, parses a filepath into an object. | homepage - path-ends-with: Return
true
if a file path ends with the given string/suffix. | homepage - path-segments: Get n specific segments of a file path, e.g. first 2, last 3, etc. | homepage
- rewrite-ext: Automatically re-write the destination extension of a filepath based on the source extension. e.g… more | homepage
- unixify: Convert Windows file paths to unix paths. | homepage
Contributing
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Contributors
Commits | Contributor |
---|---|
31 | jonschlinkert |
1 | phated |
Building docs
(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)
To generate the readme, run the following command:
$ npm install -g verbose/verb#dev verb-generate-readme && verb
Running tests
Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:
$ npm install && npm test
Author
Jon Schlinkert
License
Copyright © 2017, Jon Schlinkert. Released under the MIT License.
This file was generated by verb-generate-readme, v0.4.3, on March 29, 2017.