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

r6

v2.0.0

Published

Allows loading local modules using paths relative to a context path. This eliminates the frustration of require() using paths relative to the current file. This can be a pain when doing some very deep references, or when moving files around.

Downloads

1

Readme

The name "r6" is simply a numeronym of "require". In this case, 'r' followed by 6 letters.

How to install
npm install r6
How to use
var r6 = require('r6')({ options });
Options
  • contextPath: The root directory to search from. If not specified, r6 will use the directory of your main js file (entry point).
  • useGlobal: Assigns the r6 function to the global scope as "r6" and returns undefined. This prevents you from having to re-require r6 in all js files.
  • legacy: Utilizes local module search, and allows for the omitting of a leading forward-slash '/' for local modules. This is to retain backwards-compatibility, but it's use is not recommended.
Examples
// Instead of...
var fu = require('../../../../fight/kung');


// Loads module using the main js file's directory as the context
var r6 = require('r6')();
var fu = r6('/fight/kung');


// Use with installed modules if you want
// (In this case, the "optimize" option is suggested)
var r6 = require('r6')({ contextPath: __dirname });
var fu = r6('/fight/kung');
var path = r6('path');


// Use as a global
// File #1
require('r6')({ contextPath: __dirname, useGlobal: true });
var fu = r6('/fight/kung');

// File #2
var booty = r6('/pirate/booty')
Change Log

2.0.0

  • Removed optimize option and made leading slashes mandatory
  • Added legacy option for backwards-compatibility