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 🙏

© 2026 – Pkg Stats / Ryan Hefner

from-root

v1.0.4

Published

A module that helps building paths from project's root folder

Downloads

21

Readme

from-root

Uses find-root module to help build paths from project's root folder.

usage

Say you have this folder structure:

  • project/
    • package.json
    • conf/
      • config.js
    • services/
      • twitter-stream/
        • worker.js

worker.js could load conf.js this way:

const fromRoot = require('from-root');
const config = require(fromRoot("conf","config.js"));

instead of:

const config = require("../../conf/config.js"));

Indeed, if the location of worker.js changes, but the conf folder keeps its location, we'd have to update the require relative path.

Furthermore, fromRoot("conf","config.js") makes it clear where the required file is.

installation

> npm install from-root

migration

You may want to try this script to migrate to from-root.

N.B.: Make sure you can safely role back as changes are made in place. The script is still naive and works only if all your relative paths go back to the root folder.

cd your_project/
npm i -g from-root
find -name "*.js" | xargs grep "\.\." | cut -f"1" -d":" | xargs migrate-files-to-from-root

see also