Modern Full-Stack Development

 Path  (path)
You’ll notice that in several modules discussed thus far, you need to reference file and 
directory paths. Node provides some additional functions for working with them housed 
in the Path module.
For example, the path.basename() method returns the last portion of a path:
path.basename("/my/path/index.htm"); // "index.html"
By contrast, if you want just the path portion:
path.dirname("/my/path/index.htm"); // "/some/path"
And if you just want the extension:
path.extname("/my/path/index.htm"); // ".htm"
Finally, the path.parse() method is handy for, in a way, doing in one call what all of 
those do, plus a bit more:
path.parse("/home/users/mydata/accounts.dat");
This will return you an object in the form:
{ root : "/", dir : "/home/users/mydata",
  base : "accounts.dat", ext : ".dat", name : "accounts" }
If you need to know the platform-specific path delimiter (; for windows and : for 
∗nix 
systems), then you can get the value from the path.delimiter property.
Then there is the path.join() method which joins path segments into a final form 
that uses the platform-specific separator automatically (this example is on a Windows 
system):
path.join("/my", "path", "index.htm"); // "my\path\index.htm"
Because it is common to have to build paths dynamically in code, and because that 
process can result in munged string easily, Node offers a helpful method to deal with 
such issues in the path.normalize() method:
path.normalize("C:////tmp\\/\\/dat.md") // "C:\\temp\\dat.md"
Chapter 2   a Few More words: advanCed node and npM

---

36
Here, assume that some logic produced the string passed to path.normalize(), and 
that logic has to take a lot of things into account, so it can wind up with some sequences 
as you see that need to be reduced down to platform-specific and valid sequences. That’s 
what path.normalize() can do for you.