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

rqr

v0.0.5

Published

App root-resolving convenience wrapper for require.

Downloads

31

Readme

rqr.js

App root-resolving convenience wrapper for require in NodeJS apps.

We have found this simple wrapper around the default require statement to be extremely helpful in building our NodeJS apps. The simple premise is to allow require statements to be based on your app's root directory rather than relative to the current module. By virtue of the fact that the node_modules folder sits directly underneath your app root, we can easily wrap require with this base path and allow you to specify only a top-level directory and subpath to the desired module you want to require.

Simplest example...

var rqr = require('rqr'),
    Author = rqr('schemas/author');

This statement would work inside any module no matter how deeply nested within your app's folder structure if the schemas folder exists (as in this example) at the top/root level within your app.

Using withPrefix()

If your project folder tree goes several levels deep, use withPrefix() to create an rqr object based at a prefixed lower level...

var rqrSchemas = require('rqr').withPrefix('schemas'),
    Author = rqrSchemas('author');

Using withRoot()

If you need to include a parallel project outside of your project folder tree, use withRoot() to set a full base path for your rqr object...

var rqrProjectB = require('rqr').withRoot('~/node-apps/project-b/'),
    ModelB = rqrProjectB('schemas/model-b');

Contributing

We aim to keep this module extremely simple and free of dependencies but if you have a super cool idea to extend the capabilities with elegant, dependency-free improvements, feel free to fork and submit your pull request.

Enjoy!