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

koa-r

v1.0.4

Published

requesting node modules from one central object

Downloads

17

Readme

koa-r

Requesting node modules from some proxy object;

Installation

npm install koa-r

Example

var r = require('koa-r').isGlobal(true);
r.set('someModule', require('path/to/someModule'));
// etc...

// and then when you need to call some function from loaded module
r('someModule', 'someFn')();

As you can see we need to specify key and value for some module, and after that we can access to loaded module from some other place. Note that if isGlobal option is setted to true, we don't need to require koa-r twice. We need to require it only once, and after that it will in GLOBAL.r variable.

I am using this module in combination with koa-router. My idea is to separate routes definitions into multiple files, and then from one central place to mount routes to some url paths. Before that we set to koa-r all required dependencies for executing route callbacks, so we can call easily functions which are handling some routes. Example:

// some/path/handlers/user.js
exports.getUsers = function * (next) {
  // some code here...
  yield next;
}
// some/path/router/index.js
var mount = require('koa-mount'),
  r = require('koa-r').isGlobal(true),
  userAPI = require('some/path/router/user.js');

r.set('user', require('/some/path/handlers/user'));
// etc...

module.exports = function (app) {
  app.use(mount('/api/user/', userAPI.middleware()));
  // etc...
};
// some/path/router/user.js
var Router = require('koa-router'),
  api = new Router();

api.get('/users', r('user', 'getUsers'));
module.exports = api;

When user visits api/user/users url, function getUsers from user module will handle this route.

License

MIT