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 🙏

© 2026 – Pkg Stats / Ryan Hefner

local-modules

v1.0.1

Published

require local modules with absolute path

Downloads

8

Readme

local-modules

require local modules with absolute path

problem

require local modules in node can be annoying with relative paths. e.g.

    var cache = require('../../../plugins/cache');

detailed problem description and discussion as well as different solutions can be found here:

better local require paths

solution / hack

treat specific application folders like the node_modules folder, so that we can require stuff without ugly relative paths.

###install npm install local-modules --save

###use

with the given project structure:

    .
    ├── index.js
    ├── package.json
    ├── components
    │   └── components-test
    │       └── index.js
    ├── lib
    │   ├── lib-test
    │   │   ├── package.json
    │   │   └── test.js
    │   └── plugins
    │       ├── cache
    │       │   ├── index.js
    │       │   └── lru
    │       │       └── index.js
    │       └── index.js
    └── node_modules
        └── test
            └── index.js

you can require this from the app directory:

    // only call this once
    require('local-modules')('lib', 'components');

    // require from node_modules as usual
    require('test');

    // require from lib with absolute paths
    require('lib-test');
    require('plugins/cache');

    // require from components directory directly
    require('components-test');

or within the lib/plugins/cache/lru/index.js file, you can require this:


    require('plugins');
    require('lib-test');
    require('components-test');

test

tested so far with node 0.8, 0.10, 0.11

  1. clone the repo
  2. run node test

inspiration

https://gist.github.com/branneman/8048520

credits

  • @branneman for the great article on this topic
  • @joelabair for the cool hack