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

imported

v2.2.1

Published

Node.JS global require helper

Downloads

104

Readme

imported

Node.JS global require

Summary

This module will help clean your module dependencies by eliminating the need to require every single module in your project using relative paths.

With 'imported', you simply initialize it with a project directory name, and imported will scan your project and load every module for you. Then you simply have to request any module in your project by its name without any paths.

Update

With version 2.x, I have removed fuzzy matching to simplify the algorithm. Now, you must ensure your project has no file name collisions. This will make it easier for you to get any dependency in your project by using the file name only.

Installation

npm install imported

Usage

Assuming your directory structure looks as follows:

mainProjectDir
    |
    |
    -> start.js
    subDirectoryA
        |
        -> myfileA.js
        -> myfileB.js
        |
        |
        subDirectoryB
            |
            |
            -> myfileC.js

myfileC.js

module.exports = {
    run: run
};

function run(){
    console.log('Hi');
}

start.js

var req = require('imported').init('subDirectoryA');

var myfileC = req.get('myfileC');
var myfileA = req.get('myfileA');
var myfileB= req.myFileB; // Optional notation.

myfileC.run();

Output: 'Hi'

myFileB.js

var dep = require('imported');
var myFileC = dep.get('myFileC');

function runme() {
    var myFileA = dep.get('myFileA'); // import any module from any other module
    var myFileB = dep.myFileB; // import any module from any other module

    myFileC.run();
}

Output: 'Hi'

API

init required

Initialize module and process directory.

var req = require('imported').init('subDirectoryA');
var req = require('imported').init('subDirectoryA', {exclude: /(\.git|\.svn|node_modules|test)/ }); // Exclude option will not import those directories. Use Regex.
var req = require('imported').init(); // Optional parameter. Defaults to current directory.

Pass in an object instead to manually override dependencies. Used for mocking dependencies during unit testing.

var req = require('imported').init({
    myFileC: {
        run: function() {
            console.log('this is a mock function that overrides dependencies');
        }
    }
});

Optionally, you can also override only specific dependencies using the optional parameter: 'override'

// Will allow all normal dependencies except override the ones specified by the override parameter
var req = require('../imported').init('.', {
    override: {
        myFileC: {
            run: function() {
                console.log('run mock');
            }
        }
    }
});

Default exclusion directories:

/(\.git|\.svn|node_modules)/

get

Primary method used to import a module

var req = require('imported');

var myfileC = req.myfileC;
var myfileA = req.get('myfileA'); // Optional get function instead.

Features

  • Require any module in your entire project using the file's name
  • Will recusively search your project for the module you are requesting
  • Throws an error when 'requiring' a dependency that does not exist
  • Throws an error when a naming collision is detected
  • Collision detection
  • Unit testing coverage on all interfaces for helper functions
  • Directory exclusion

Future

  • Easy dependency override for unit testing mocking