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

getmodule

v1.0.0

Published

Include local modules relative to your root path

Downloads

40

Readme

Get Module

Include local NodeJS modules relative to your root path

NPM version Build Status Coverage Status Code Climate

NPM

Installation

npm i --save getmodule

Usage

Add getmodule on top of your app.js (or main file of your app):

require( 'getmodule' );

Now, you can call any module based on root path of your application.

If your module is on app/modules/mymodule.js, but you're calling it on the file app/controllers/controller.js; in tradicional mode, you needed to do:

var mymodule = require( '../modules/mymodule' );

But with getmodule, you just need type this:

var mymodule = getmodule( 'app/modules/mymodule' );

Contributing

Check CONTRIBUTING.md

License

MIT License © Fernando Daciuk