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

package-root

v0.9.2

Published

Generate paths relative to your package's source root

Downloads

11

Readme

package-root

Is your application or package suffering from relative-path Hell? Do your require statements look like the following?

var config           = require("../../../config"           );
var middleware       = require("../../../lib/middleware"   );
var users_controller = require("../../../controllers/users");

Don't worry -- package-root is here to help! With package-root, you can generate package-relative paths with ease!

var pr = require('package-root');

var config           = pr("config");
var middleware       = pr("lib/middleware");
var users_controller = pr("controllers/users");

There -- I bet you feel better already!

Installation

npm install package-root

Usage

Setup

package-root discovers your package's root by searching for a file named __package_root. For example, let's imagine that our application / package is structured as follows:

.
├── package.json
└── src
    ├── config.json
    ├── controllers
    │   ├── index.js
    │   └── users.js
    └── mw
        ├── auth.js
        └── index.js

Since the package's code lives in the src/ folder, we'll want to place the ___package_root file there. Afterwards, the filesystem will look like this:

.
├── package.json
└── src
    ├── config.json
    ├── controllers
    │   ├── index.js
    │   └── users.js
    ├── mw
    │   ├── auth.js
    │   └── index.js
    └── __package_root

Package-relative require statements

Now that you've planted the __package_root file in the appropriate location, you can perform package-relative requires as follows:

var pr = require('package-root');

// Path is relative to src/
var config = pr("config");

Package-relative path joins

Of course, maybe you just want to obtain the path to some file in your package. You can achieve this by using the join function:

var pr = require('package-root');

// Generate the path to the package's config.json file
var config_path = pr.join("config.json");

Just like path.join, package-root's join function can accept a variable number of arguments:

var users_controller_path = pr.join("controllers", "users.js");

Pretty simple, huh?