This module contains utilities for handling and transforming file\npaths. Almost all these methods perform only string transformations.\nThe file system is not consulted to check whether paths are valid.
\nUse require('path') to use this module. The following methods are provided:
Return the last portion of a path. Similar to the Unix basename command.
Example:
\npath.basename('/foo/bar/baz/asdf/quux.html')\n// returns 'quux.html'\n\npath.basename('/foo/bar/baz/asdf/quux.html', '.html')\n// returns 'quux'\nReturn the directory name of a path. Similar to the Unix dirname command.
Example:
\npath.dirname('/foo/bar/baz/asdf/quux')\n// returns '/foo/bar/baz/asdf'\nReturn the extension of the path, from the last '.' to end of string\nin the last portion of the path. If there is no '.' in the last portion\nof the path or the first character of it is '.', then it returns\nan empty string. Examples:
\npath.extname('index.html')\n// returns '.html'\n\npath.extname('index.coffee.md')\n// returns '.md'\n\npath.extname('index.')\n// returns '.'\n\npath.extname('index')\n// returns ''\n\npath.extname('.index')\n// returns ''\nReturns a path string from an object, the opposite of [path.parse][].
Examples:
\nSome Posix system examples:
\n// If `dir` and `base` are provided, `dir` + platform separator + `base`\n// will be returned.\npath.format({\n dir: '/home/user/dir',\n base: 'file.txt'\n});\n// returns '/home/user/dir/file.txt'\n\n// `base` will be returned if `dir` or `root` are not provided.\npath.format({\n base: 'file.txt'\n});\n// returns 'file.txt'\nDetermines whether path is an absolute path. An absolute path will always\nresolve to the same location, regardless of the working directory.
Posix examples:
\npath.isAbsolute('/foo/bar') // true\npath.isAbsolute('/baz/..') // true\npath.isAbsolute('qux/') // false\npath.isAbsolute('.') // false\nWindows examples:
\npath.isAbsolute('//server') // true\npath.isAbsolute('C:/foo/..') // true\npath.isAbsolute('bar\\\\baz') // false\npath.isAbsolute('.') // false\nNote: If the path string passed as parameter is a zero-length string, unlike\n other path module functions, it will be used as-is and false will be\n returned.
Join all arguments together and normalize the resulting path.
\nArguments must be strings. In v0.8, non-string arguments were\nsilently ignored. In v0.10 and up, an exception is thrown.
\nExample:
\npath.join('/foo', 'bar', 'baz/asdf', 'quux', '..')\n// returns '/foo/bar/baz/asdf'\n\npath.join('foo', {}, 'bar')\n// throws exception\nTypeError: Arguments to path.join must be strings\nNote: If the arguments to join have zero-length strings, unlike other path\n module functions, they will be ignored. If the joined path string is a\n zero-length string then '.' will be returned, which represents the\n current working directory.
Normalize a string path, taking care of '..' and '.' parts.
When multiple slashes are found, they're replaced by a single one;\nwhen the path contains a trailing slash, it is preserved.\nOn Windows backslashes are used.
\nExample:
\npath.normalize('/foo/bar//baz/asdf/quux/..')\n// returns '/foo/bar/baz/asdf'\nNote: If the path string passed as argument is a zero-length string then '.'\n will be returned, which represents the current working directory.
Returns an object from a path string.
\nAn example on *nix:
\npath.parse('/home/user/dir/file.txt')\n// returns\n// {\n// root : "/",\n// dir : "/home/user/dir",\n// base : "file.txt",\n// ext : ".txt",\n// name : "file"\n// }\nAn example on Windows:
\npath.parse('C:\\\\path\\\\dir\\\\index.html')\n// returns\n// {\n// root : "C:\\\\",\n// dir : "C:\\\\path\\\\dir",\n// base : "index.html",\n// ext : ".html",\n// name : "index"\n// }\nSolve the relative path from from to to.
At times we have two absolute paths, and we need to derive the relative\npath from one to the other. This is actually the reverse transform of\npath.resolve, which means we see that:
path.resolve(from, path.relative(from, to)) == path.resolve(to)\nExamples:
\npath.relative('C:\\\\orandea\\\\test\\\\aaa', 'C:\\\\orandea\\\\impl\\\\bbb')\n// returns '..\\\\..\\\\impl\\\\bbb'\n\npath.relative('/data/orandea/test/aaa', '/data/orandea/impl/bbb')\n// returns '../../impl/bbb'\nNote: If the arguments to relative have zero-length strings then the current\n working directory will be used instead of the zero-length strings. If\n both the paths are the same then a zero-length string will be returned.
Resolves to to an absolute path.
If to isn't already absolute from arguments are prepended in right to left\norder, until an absolute path is found. If after using all from paths still\nno absolute path is found, the current working directory is used as well. The\nresulting path is normalized, and trailing slashes are removed unless the path\ngets resolved to the root directory. Non-string from arguments are ignored.
Another way to think of it is as a sequence of cd commands in a shell.
path.resolve('foo/bar', '/tmp/file/', '..', 'a/../subfile')\nIs similar to:
\ncd foo/bar\ncd /tmp/file/\ncd ..\ncd a/../subfile\npwd\nThe difference is that the different paths don't need to exist and may also be\nfiles.
\nExamples:
\npath.resolve('/foo/bar', './baz')\n// returns '/foo/bar/baz'\n\npath.resolve('/foo/bar', '/tmp/file/')\n// returns '/tmp/file'\n\npath.resolve('wwwroot', 'static_files/png/', '../gif/image.gif')\n// if currently in /home/myself/node, it returns\n// '/home/myself/node/wwwroot/static_files/gif/image.gif'\nNote: If the arguments to resolve have zero-length strings then the current\n working directory will be used instead of them.
The platform-specific path delimiter, ; or ':'.
An example on *nix:
\nconsole.log(process.env.PATH)\n// '/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin'\n\nprocess.env.PATH.split(path.delimiter)\n// returns ['/usr/bin', '/bin', '/usr/sbin', '/sbin', '/usr/local/bin']\nAn example on Windows:
\nconsole.log(process.env.PATH)\n// 'C:\\Windows\\system32;C:\\Windows;C:\\Program Files\\node\\'\n\nprocess.env.PATH.split(path.delimiter)\n// returns ['C:\\\\Windows\\\\system32', 'C:\\\\Windows', 'C:\\\\Program Files\\\\node\\\\']\nProvide access to aforementioned path methods but always interact in a posix\ncompatible way.
The platform-specific file separator. '\\\\' or '/'.
An example on *nix:
\n'foo/bar/baz'.split(path.sep)\n// returns ['foo', 'bar', 'baz']\nAn example on Windows:
\n'foo\\\\bar\\\\baz'.split(path.sep)\n// returns ['foo', 'bar', 'baz']\nProvide access to aforementioned path methods but always interact in a win32\ncompatible way.