requireg

Require and resolve global modules in node.js like a boss.

Differences with require()

requireg tries to find modules in global locations which are not natively supported by the node.js module resolve algorithm.

It support both npm/yarn global packages installation paths.

Supported locations:

$ npm install requireg --save[-dev]

$ yarn add requireg

var requireg = require('requireg')
// require a globally installed package
var npm = requireg('npm')

var requireg = require('requireg')
// require a globally installed package and skip local packages
var eslint = requireg('eslint', true)

var modulePath = requireg.resolve('npm')
// returns '/usr/local/lib/node_modules/npm/lib/npm.js'

require('requireg').globalize()

Now it is globally available from any source file

var globalModule = requireg('npm')

requireg maintains the same behavior as the native require(). It will throw an Error exception if the module was not found

Require global modules in node.js is considered anti-pattern. Note that you can experiment unreliability or inconsistency across different environments. I hope you know exactly what you do with requireg
Only node packages installed with npm or yarn are supported (which means only standardized NPM paths are supported)

Released under MIT license