npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nice-path

v2.0.0

Published

`nice-path` provides a class that represents a filesystem path (POSIX-style or Win32-style), which has various nice methods on it that make it easy to work with. It can be used as a replacement for the Node.js `path` builtin module, where you pass around

Downloads

31

Readme

nice-path

nice-path provides a class that represents a filesystem path (POSIX-style or Win32-style), which has various nice methods on it that make it easy to work with. It can be used as a replacement for the Node.js path builtin module, where you pass around Path objects and stringify them before use, rather than passing around strings.

Example

import { Path } from "nice-path";

const here = new Path(__dirname);
console.log(here);
// Path {
//   segments: ["", "home", "suchipi", "Code", "nice-path"],
//   separator: "/"
// }

here.toString(); // "/home/suchipi/Code/nice-path"
here.isAbsolute(); // true

const readme = here.concat("README.md");
console.log(readme);
// Path {
//   segments: [
//     "",
//     "home",
//     "suchipi",
//     "Code",
//     "nice-path",
//     "README.md"
//   ],
//   separator: "/"
// }
readme.basename(); // "README.md"
readme.extname(); // ".md"
readme.dirname(); // Path object with same contents as 'here'

// normalize resolves . and .. components
const homeDir = here.concat("../../.").normalize();
console.log(homeDir);
// Path {
//   segments: [
//     "",
//     "home",
//     "suchipi"
//   ],
//   separator: "/"
// }

here.relativeTo(homeDir).toString(); // "./Code/nice-path"
readme.relativeTo(homeDir).toString(); // "./Code/nice-path/README.txt"

// There are also several other methods which aren't in this example.

API Documentation

Overview

This package has one named export: "Path", which is a class.

The "Path" class has the following instance properties:

  • segments (Array of string)
  • separator (string)

and the following instance methods:

  • normalize
  • concat
  • isAbsolute
  • clone
  • relativeTo
  • toString
  • basename
  • extname
  • dirname
  • startsWith
  • endsWith
  • indexOf
  • includes
  • replace
  • replaceAll
  • replaceLast

and the following static methods:

  • splitToSegments
  • detectSeparator
  • normalize
  • isAbsolute
  • fromRaw

Details

Path (class)

An object that represents a filesystem path. It has the following constructor signature:

class Path {
  constructor(...inputs: Array<string | Path | Array<string | Path>>);
}

You can pass in zero or more arguments to the constructor, where each argument can be either a string, a Path object, or an array of strings and Path objects.

When multiple strings/Paths are provided to the constructor, they will be concatenated together in order, left-to-right.

The resulting object has two properties: segments, which is an array of strings containing all the non-slash portions of the Path, and separator, which is the slash string that those portions would have between them if this path were represented as a string.

segments: Array<string> (instance property of Path)

Each Path object has a segments property, which is an array of strings containing all the non-slash portions of the Path.

For example, given a path object myPath = new Path("a/b/c/d"), myPath.segments is an array of strings ["a", "b", "c", "d"].

You may freely mutate this array in order to add or remove segments, but I recommend you instead use instance methods on the Path object, which take a "separator-aware" approach to looking at path segments.

POSIX-style absolute paths start with a leading slash character, like "/a/b/c". A Path object representing that path, (ie new Path("/a/b/c")) would have the following path segments:

["", "a", "b", "c"]

That empty string in the first position represents the "left side" of the first slash. When you use .toString() on that Path object, it will become "/a/b/c" again, as expected.

Windows UNC paths have two empty strings at the beginning of the Array.

separator: string (instance property of Path)

Each Path object has a separator property, which is the slash string that those portions would have between them if this path were represented as a string. It's always either / (forward slash) or \ (backward slash). If you change this property, the result of calling .toString() on the Path object will change:

// The initial value of separator is inferred from the input path:
const myPath = new Path("hi/there/friend");
console.log(myPath.separator); // prints /

// Using toString() joins the path segments using the separator:
console.log(myPath.toString()); // prints hi/there/friend

// If you change the separator... (note: this is a single backslash character. It has to be "escaped" with another one, which is why there are two.)
myPath.separator = "\\";

// Then toString() uses the new separator instead:
console.log(myPath.toString()); // prints hi\there\friend

The initial value of the separator property is inferred by searching the input string(s) the Path was constructed with for a slash character and using the first one found. If none is found, a forward slash (/) is used.

normalize(): Path (instance method of Path)

The normalize method returns a new Path with all non-leading . and .. segments resolved.

const myPath = new Path("/some/where/../why/over/./here");
const resolved = myPath.normalize();
console.log(resolved.toString()); // /some/why/over/here

If you want to evaluate a relative path (a path with leading . or .. segments) using a base directory, you can concatenate and then normalize them:

const baseDir = new Path("/home/me");
const relativeDir = new Path("./somewhere/something/../blue");
const resolved = baseDir.concat(relativeDir).normalize();
console.log(resolved.toString()); // /home/me/something/blue

concat(...others): Path (instance method of Path)

The concat method creates a new Path by appending additional path segments onto the end of the target Path's segments. The additional path segments are passed to the concat method as either strings, Paths, or Arrays of strings and Paths.

The new Path will use the separator from the target Path.

const pathOne = new Path("a/one");
const withStuffAdded = pathOne.concat(
  "two",
  "three/four",
  new Path("yeah\\yes"),
);

console.log(withStuffAdded.toString());
// "a/one/two/three/four/yeah/yes"

isAbsolute(): boolean (instance method of Path)

The isAbsolute method returns whether the target Path is an absolute path; that is, whether it starts with either /, \, or a drive letter (ie C:).

clone(): Path (instance method of Path)

The clone method makes a second Path object containing the same segments and separator as the target.

relativeTo(dir, options?): Path (instance method of Path)

The relativeTo method expresses the target path as a relative path, relative to the dir argument.

The options argument, if present, should be an object with the property "noLeadingDot", which is a boolean. The noLeadingDot option controls whether the resulting relative path has a leading . segment or not. If this option isn't provided, the leading dot will be present. Note that if the resulting path starts with "..", that will always be present, regardless of the option.

toString(): string (instance method of Path)

The toString method returns a string representation of the target Path by joining its segments using its separator.

basename(): string (instance method of Path)

The basename method returns the final segment string of the target Path. If that Path has no segments, the empty string is returned.

extname(options?): string (instance method of Path)

The extname method returns the trailing extension of the target Path. Pass { full: true } as the "options" argument to get a compound extension like ".d.ts", rather than the final extension (like ".ts").

If the Path doesn't have a trailing extension, the empty string ("") is returned.

dirname(): Path (instance method of Path)

The dirname method returns a new Path containing all of the segments in the target Path except for the last one; ie. the path to the directory that contains the target path.

startsWith(value): boolean (instance method of Path)

The startsWith method returns whether the target Path starts with the provided value (string, Path, or Array of string/Path), by comparing one path segment at a time, left-to-right.

The starting segment(s) of the target Path must exactly match the segment(s) in the provided value.

This means that, given two Paths A and B:

  A: Path { /home/user/.config }
  B: Path { /home/user/.config2 }

Path B does not start with Path A, because ".config" !== ".config2".

endsWith(value): boolean (instance method of Path)

The endsWith method returns whether the target Path ends with the provided value (string, Path, or Array of string/Path), by comparing one path segment at a time, right-to-left.

The ending segment(s) of the target Path must exactly match the segment(s) in the provided value.

This means that, given two Paths A and B:

  A: Path { /home/1user/.config }
  B: Path { user/.config }

Path A does not end with Path B, because "1user" !== "user".

indexOf(value, fromIndex?): number; (instance method of Path)

The indexOf method returns the path segment index (number) at which value (string, Path, or Array of string/Path) appears in the target Path, or -1 if it doesn't appear.

If the provided value argument contains more than one path segment, the returned index will refer to the location of the value's first path segment.

The optional argument fromIndex can be provided to specify which index into the target Path's segments to begin the search at. If not provided, the search starts at the beginning (index 0).

includes(value, fromIndex?): boolean; (instance method of Path)

The includes method returns a boolean indicating whether value (string, Path, or Array of string/Path) appears in the target Path.

The optional argument fromIndex can be provided to specify which index into the target Path's segments to begin the search at. If not provided, the search starts at the beginning (index 0).

replace(value, replacement): Path; (instance method of Path)

The replace method returns a new Path object wherein the first occurrence of value (string, Path, or Array of string/Path) in the target Path has been replaced with replacement (string, Path, or Array of string/Path).

Note that only the first match is replaced; to replace multiple occurrences, use replaceAll.

If value is not present in the target Path, a clone of said Path is returned.

Tip: To "replace with nothing", pass an empty array as the replacement.

replaceAll(value, replacement): Path; (instance method of Path)

The replaceAll method returns a new Path object wherein all occurrences of value (string, Path, or Array of string/Path) in the target Path have been replaced with replacement (string, Path, or Array of string/Path).

If you want to only replace the first occurrence, use replace instead.

If value is not present in the target Path, a clone of said Path is returned.

Tip: To "replace with nothing", pass an empty array as the replacement.

replaceLast(replacement): Path; (instance method of Path)

The replaceLast method returns a copy of the target Path, but with its final segment replaced with replacement (string, Path, or Array of string/Path).

This method is most commonly used to modify the final (filename) part of a path.

If the target Path has no segments, the returned Path will contain exactly the segments from replacement.

Path.splitToSegments(inputParts): Array<string> (static method on Path)

Splits one or more path strings into an array of path segments. Used internally by the Path constructor.

Path.detectSeparator(input, fallback) (static method on Path)

Searches input (a string or Array of strings) for a path separator character (either forward slash or backslash), and returns it. If none is found, returns fallback.

Path.normalize(...inputs): Path (static method on Path)

Concatenates the input path(s) and then resolves all non-leading . and .. segments. Shortcut for new Path(...inputs).normalize().

Path.isAbsolute(path): boolean (static method on Path)

Return whether the path argument (string or Path) is an absolute path; that is, whether it starts with either /, \, or a drive letter (ie C:).

Path.fromRaw(segments, separator): Path (static method on Path)

Creates a new Path object using the provided segments and separator.

License

MIT