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

@root/path

v1.1.0

Published

A secure-by-default path module (wrapper around node's path)

Downloads

5

Readme

@root/path

A secure-by-default path module (wrapper around node's path).

npm install --save @root/path
var Path = require("@root/path");

// throws error when path resolves to ../...
Path.join("foo", "../bar"); // throws error
Path.resolve("/foo", "/bar"); // throws error
Path.relative("/foo/bar", "/foo"); // throws error

// unsafe is an alias to require('path'), for convenience;
Path.unsafe.join("foo", "../bar"); // does NOT throw error

Use with Promises, if you prefer:
(not actually async, but makes error handling easier via .catch()):

var Path = require("@root/path").promises;

Path.join("foo", "../bar").catch(function (e) {
  // give empty string rather than throwing error
  return "";
});

await Path.unsafe.join("foo", "../bar");

Note: v1.x does not check fs.realpath to resolve symbolic links. You probably know if you're using symbolic links, so if you're using potentially dangerous symbolic links, you need to check fs.realpath yourself.

API

Same as the built-in path, but throws an error when a joined, resolved, or relative path is not a child of the root, base, or from path.

{
  "message": "'x' [may] resolve[s] to a different parent than 'y'",
  "code": "E_PARENT_PATH",
  "path": "x"
}

Path.join(root, child1, ...)

Throw an error if the new path is not a child of root:

// Good
Path.join("/foo", "/bar"); //=> /foo/bar
Path.join("/foo", "./bar"); //=> /foo/bar
Path.join("/foo", "bar"); //=> /foo/bar
Path.join("foo", "bar"); //=> foo/bar

// Bad
Path.join("../foo", "bar"); //X ../foo/bar
Path.join("foo", "../bar"); //X ./bar

Path.resolve(base, path1, ...)

Throw an error if the new path is is not a child of base:

// Good
Path.resolve("/foo", "./bar"); //=> /foo/bar
Path.resolve("/foo", "bar"); //=> /foo/bar
Path.resolve("foo", "bar"); //=> /Users/me/foo/bar
Path.resolve("../foo", "bar"); // /Users/foo/bar

// Bad
Path.resolve("/foo", "/bar"); //X /bar
Path.resolve("foo", "../bar"); //X /Users/me/bar

Path.relative(from, to)

Throw an error if to resolves outside of from (i.e. the path starts with ..):

// Good
Path.relative("/foo/bar", "/foo/bar/baz"); //=> bar
Path.relative("/foo", "/foo/bar/baz"); //=> bar/baz
Path.relative("foo", "foo/bar"); //=> bar

// Bad
Path.relative("foo", "bar"); //X ../bar
Path.relative("/foo", "bar"); //X ../Users/me/bar
Path.relative("/foo/bar", "/foo"); //X ..
Path.relative("../foo", "bar"); // //X ../me/bar

Extra

The rest of path's properties are provided for convenience, but their behavior is left unchanged.

See https://nodejs.org/api/path.html

The non-wrapped methods and properties are generated automatically, so this module will mirror the built-in path without being republished.