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

require-root

v1.0.0

Published

A utility for dealing with relative require paths in a Node project

Downloads

7

Readme

require-root

A utility for dealing with relative require paths in a Node project

Example usage:

In the directory that you think of as the root of the code you are writing, touch a file called .root

In that directory or any directory under that directory (subdir, subdir of a subdir, etc.), instead of doing something like this:

myLib = require('../../myLib')

You can do

// Assumes you `touch`ed example.root in the same dir as myLib.js
requireExample = require('require-root')('example')
myLib = requireExample('myLib')

And not worry about how far up the directory tree you need to go or rewriting all your ../s if you move things around

Or instead of

myModelLib = require('../../model/myLib')

You can do

requireExample = require('require-root')('example')
myModelLib = requireExample('model/myLib') // './model/myLib' also fine

For more advanced usage, you can put JSON in your .root file instead of just leaving it empty, and configure where exactly the root is -- if it isn't just in the same directory as your .root file, ex.

model.root:
    {"rootPath":"./model/"}

Or

some-code-somewhere-totally-different-on-my-filesystem.root:
    {"rootPath":"/absolute/path/to/somewhere/totally/different"}

There is also an analog of require.resolve, so you can do

requireExample = require('require-root')('example')
pathToFile = requireExample.resolve('myLib')

There's no problem working with multiple require-resolves in the same file. Ex.

requireResolve = require('require-resolve')
requireModel = requireResolve('model')
requireView = requireResolve('view')
requireController = requireResolve('controller')

The resolution and reading of the .root files is cached, and should only have to happen once per require-resolve, so this shouldn't cause any performance problems under most circumstances.

A more detailed, concrete example, (from the test/ directory of this package)

Given a directory structure that looks like this:

.
└── alpha
    ├── bravo
    │   ├── charlie
    │   │   └── index.js
    │   ├── delta
    │   │   └── my-module.js
    │   ├── example2.root
    │   └── my-module.js
    ├── example.root
    └── my-module.js

when ./alpha/bravo/charlie/index.js

contains the code

requireRoot = require('../../../../index')

requireExample = requireRoot('example')
requireExample2 = requireRoot('example2')

console.log('example#my-module', requireExample('my-module'))
console.log('example2#my-module', requireExample2('my-module'))
console.log('example#bravo/my-module', requireExample('bravo/my-module'))

will result in this output:

example#my-module { success: true }
example2#my-module { moreSuccess: true }
example#bravo/my-module { success3: true }

The data structures logged are the module.exports from ./alpha/my-module.js ./alpha/bravo/delta/my-module.js ./alpha/bravo/my-module.js respectively