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

root_require

v0.0.0

Published

Hijacks node's module resolution so that you can use a prefixed path to require modules from the project root.

Downloads

10

Readme

root_require

Hijacks node's module resolution so that you can use a prefixed path to require modules from the project root.

If you want to accomplish this by transforming your code rather than using this runtime node hack, or for bundling for the browser, use babel-plugin-root-require.

install

$ npm install root_require

example

require('root_require').setRoot()

const myThing = require('~/things/relatively')

Starting from your project root, if you have a file lib/foo.js and you want to require it from routes/user/profile, you would normally write require('../../../lib/foo'). With root_require initialized, you can just write require('~/lib/foo') from anywhere.

api

setRoot(pathToRoot)

If no argument is given, setRoot will look for a package.json and consider the directory it is found in to be the root.

setPrefix(prefix)

The prefix to use to refer to the project root.

require('root_require').setPrefix('TATERS').setRoot()

require('TATERS/foo.js')

reset()

Restore module resolution to default behavior. You probably don't ever need to do this.