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

path2

v0.1.0

Published

Modular and extended version of `path` package

Downloads

3,729,624

Readme

path2

Modular and extended version of Node's path package

Works exactly same as Node's path, with following improvements:

  • Both windows and posix versions can be accessed in any environment program is run. For windows version require path2/windows for posix path2/posix.
  • Doesn't depend on existence of process object and can safely be used in any enviroment (e.g. browser) which does not provide it. If process.cwd is not accessible, / or _C:_ (for windows) are used as current working directory
  • Each function is provided as an individual module, so only modules that are needed, can be required e.g. path2/resolve or specifically posix version: path2/posix/resolve

One additional function, not present in native path, is provided:

path.common(path1[, ...pathn])

Resolves common path for given path arguments:

path.common('/lorem/ipsum/foo/bar', '/lorem/ipsum/raz/dwa',
  '/lorem/elo/foo/bar'); //  => '/lorem'

path.common is proposed to be included in native path

Installation

NPM

In your project path:

$ npm install path2
Browser

You can easily bundle path2 for browser with modules-webmake

Tests Build Status

$ npm test