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

requirebase

v1.4.0

Published

Allows requiring modules relative to the base of the specified npm module (based on package.json 'name'), rather than relative to the current file.

Downloads

3

Readme

requirebase

Allows requiring modules relative to the base of the specified npm module (based on package.json 'name'), rather than relative to the current file.

The module assumes that "package.json" will be in the directory to be considered the "base" or "root" directory from which you wish to require files. "node_modules" gets created underneath this directory by npm.

It also assumes that it will be installed somewhere under the "node_modules" directory. That way, when searching up the directory chain for the appropriate "package.json", it must find the "package.json" in the base directory.

Examples of use:

// Require and properly initialize requirebase module
const requirebase = require("requirebase")("base-module-name");

// Now require some library modules (in 'lib' subdir under base dir)
const utilities = requirebase("lib/utilities");
const parser = requirebase("lib/parser");

// Require an MVC controller
const ctrlUsers = requirebase("www/mvc/controllers/users");

// Require a library module using a custom require() function
const parserRewire = requirebase("lib/parser", rewire);

Once initialized by calling the requirebase function with the desired npm module name whose package.json to consider the root/base directory, you can get the detected base directory path:

let baseDir = requirebase.getBasePath();

You can also construct a path from the combination of the detected base directory path and an extra specified path:

let mvcDir = requirebase.pathFromBase("www/mvc");

In addition, to get info from the base package.json parsed into a JavaScript object (eg. version):

let packageVersion = requirebase.getBasePackageJson().version;