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 🙏

© 2025 – Pkg Stats / Ryan Hefner

dirplus

v0.0.3

Published

Lightweight ESM-only utility for resolving absolute paths in Node.js.

Readme

Dirplus

NPM version

Lightweight ESM-only utilities for resolving absolute paths in Node.js.

dirplus gives you two tiny helpers to handle paths safely:

  • dirname(meta, ...paths) → resolve paths relative to the script file (ESM-friendly __dirname)
  • cwd(...paths) → resolve paths relative to where Node.js was executed

Features ✨

  • 🔹 Simple API – One-call path resolution.
  • 🌐 ESM-only – Built for modern Node.js.
  • Zero dependencies – Tiny, fast, reliable.
  • 🔄 Flexible – Combine multiple path segments.

Installation 💿

# npm
npm install dirplus

# pnpm
pnpm add dirplus

# yarn
yarn add dirplus

Usage 📦

import { dirname, cwd } from 'dirplus';

// dirname → relative to the script
console.log(dirname(import.meta));
// => /absolute/path/to/script

console.log(dirname(import.meta, 'data', 'file.json'));
// => /absolute/path/to/script/data/file.json

// cwd → relative to where Node was started
console.log(cwd());
// => /absolute/path/where/node/was/run

console.log(cwd('data', 'file.json'));
// => /absolute/path/where/node/was/run/data/file.json

API

  • dirname(meta: ImportMeta, ...paths: string[]): string Resolves paths relative to the script's directory. You must pass import.meta as the first argument.

  • cwd(...paths: string[]): string Resolves paths relative to the current working directory.

License 📄

MIT – see LICENSE.

Author: Estarlin R · estarlincito.com