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

path-fx

v2.1.2

Published

Path utils which don't necessarily depend on Node.js

Downloads

4,343

Readme

Standalone, stateless, bare minimum path utils for things

Standalone and stateless imply that this package works without any context, unlike Node's built-in path module which sometimes will use process.cwd() to do its thing.

If you didn't pick up already, this package is intended to be used in web apps only. And for that reason code size has been kept as little as possible.

Some differences from node's path module:

  • splitPath exported from this package splits path on each delimeter
  • Leading and trailing slashes are preserved when calling any path operation like join, normalize or relative
  • Trailing slashes can be removed using removeTrailingSlashes if you so desire

Usage

Install

npm i path-fx

Use

import {
    // platform auto-detected utils
    dirname, extname, // basename, ...
    // platform specific
    win32, unix
} from 'path-fx';

// platform auto-detected utils
console.log(dirname('/etc/ping/pong')); // > /etc/ping
console.log(extname('/etc/ping/pong/foo.js')); // > .js

// notice back slash in the output (unix delimits path(s) only on forward slashes)
console.log(unix.basename('/etc/ping/pong/foo\\bar.js')); // > foo\bar.js

// notice mixed slashes (win32 uses forward AND back slashes as folder separators)
console.log(win32.basename('C:\\etc/ping\\pong/foo\\bar.js')); // > bar.js

API defined in dist/typings/index.d.ts

Important note

This module will use navigator.platform to set initial path separator it'll use for exported functions.

~~It is advised that you set it manually with path.setPathSeparator() to be sure.~~

Moving from 1.5.1 to 2.0.0, setPathSeparator was removed as it was a global operation and was an opportunity for accidental bugs in your codebase. Instead, 2.0.0+ now exports unix and win32 objects alongside auto-detected utils.