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

easy-require

v1.0.1

Published

Wrapper around require that supports paths from the application root and requiring directories as namespaces

Downloads

3

Readme

easy-require

Wrapper around require that supports paths from the application root and requiring directories as namespaces

Code Climate Build Status Dependency Status devDependency Status

This module was mostly created to be used with large applications where you can forget where specific items are relative to where you are but you're conventions make it easy to get to them from the applications root

The ability to require an entire directory as a namespace came out of my laziness.

Usage

npm install --save easy-require

var app = {}; app.require = require('easy-require');

// require a module local to the root directory // just start it with ~/ to denote that it's relative to the app root app.require('~/modules/cart/models/tax');

// require a directory and its children as a namespace // just pass in true as the second parameter to recursively include a directory to a namespace app.require('./controllers', true); // the optional true tells it to treat the require as a namespace

// requiring anything else app.require('normal path you would include'); // everything else is just a normal require

Performance

Easy-require is extremely performant adding little overhead on the initial require It also performs significantly better than regular require when requiring the same modules in an application

Requiring a directory into a namespace is also performance oriented but can slow down with very large directory structures if you have a need for a namespace that will end up using more than 50 modules please load them at startup, additional requires after this will use a cache so you don't have the performance hit at runtime

To view cached reference performance results please look in the perf directory there is a linux, windows, and mac result available.

While the results were consistent across all of my machines this module hasn't been battle tested yet so please run tests on your own environment and codebase and open an issue if you find any discrepencies