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

elquire

v1.0.3

Published

Local Node dependencies without the hassle: require by a given name instead of a relative path.

Downloads

11

Readme

elquire

Local Node dependencies without the hassle: require by a given name instead of a relative path.

Made with ❤ at @outlandish

js-standard-style

v1.0.0 introduces a breaking change! The module now expects immediate invocation with or without options. This avoids traversing the directory structure for a first time without options, which was offered as a convenience but adds unnecessary overhead:

// If you are doing this:
require('elquire');

// You must now do this:
require('elquire')();

Usage

Install with npm:

npm install elquire --save

1. Initialise elquire

Initialise elquire at the top of your application's entry file and invoke with the desired namespace.

require('elquire')('myApp');

// Require your application:
require('./index.js');

2. Register a module

Give any local dependency in your application a module definition at the beginning of the file:

/// <module name=myApp.utility>

// ... file contents ...

3. Require a module

Finally, replace the relative path to a local dependency with its given name:

// BEFORE:
let util = require('../../util/index.js');

// AFTER:
let util = require('myApp.utility');

Ta-da! At runtime elquire will dynamically resolve the dependency's name to a relative path (the above, backwards).

Configuration

If you prefer, you can place all the options documented here within your package.json file. See an example below:

// package.json
"elquire": {
    "namespace": "myApp"
}

// initialisation without options object
require('elquire')()

namespace

Default: none

Require that all module names begin with the given string.

require('elquire')('myApp');

// or...

require('elquire')({
    namespace: 'myApp'
});

name

Default: none

A regular expression to match against all module names. elquire throws an error when a module name does not satisfy the regular expression.

// begin names with 'local.'
require('elquire')({
    name: /^local\./
});

path

Default: './'

Override this behaviour:

require('elquire')({
    path: './startInspectionHere'
});

ignore

Default: hidden folders & files (e.g. .git) and node_modules folders (['node_modules', /^\./])

Add files and folders to ignore:

require('elquire')({
    ignore: ['./doNotLookInHere']
});

All Options

require('elquire')({

    // Set the namespace
    namespace: 'myApp',

    // Ensure that all module names satisfy a regular expression
    // (this does not override `namespace`)
    name: /^myApp\./,

    // Path to the directory where elquire should operate
    // (all children of the path are inspected recursively)
    path: './path/to/application',

    // Files or directories to ignore
    // (strings should be relative to `path`)
    ignore: [
        './doNotLookInHere',
        /ignore/i
    ]
});

ES6

Imports

elquire supports ES6 import statements. For example:

import 'myApp.utility';
import * from 'myApp.utility';
import {utilMethod, anotherUtilMethod} from 'myApp.utility';
// etc.

Babel

If you are using babel-register in your application, require it before elquire in your entry file:

// entry.js
require('babel-register');
require('elquire');

// index.js
import 'myApp.utility';

Contributing

All pull requests and issues welcome! If you're not sure how, check out Kent C. Dodds' great video tutorials on egghead.io!