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 🙏

© 2025 – Pkg Stats / Ryan Hefner

node-resources

v0.1.1

Published

A helper to register routes from modules on restify and ExpressJS. Improves separation of concerns and propose a different code organization on your application.

Readme

node-resources

Build Status NPM version

History

-0.1.1 Added console log to show errors when requiring resources. Thanks to https://github.com/rstuven

Usage

When working on Restify or ExpressJS applications you usually see a file structure based on routes, models and views.

|_app.js
|_routes
| |_hello.js
|_models
| |_hello.js
|_views
  |_hello
    |_index.ejs
    |_edit.ejs

This structure is very common to other MVC frameworks as well.

I found that this structure works well for small or medium size projects but after a while it can get a bit out of control. The main problem is that code that belong together and is relate is split all over the place what makes developing small modules in isolation very complicate.

I prefer the following code organization.

|_app.js
|_resources
  |_hello
    |_index.js
    |_handlers.js
    |_models
    | |_hello.js
    |_views
      |_index.ejs
      |_edit.ejs

This approach makes each module self contained.

Caveats

You want to make sure that inter-dependency between this modules is keep to a minimum.

Usage

Install as usual via npm

npm install node-resources

To use the structure above you should do the following.

var resources = require('node-resources');
resources.registerRoutes(server, {path: __dirname + "/resources"});

Your route files should export a function that accepts the server as it's only parameter.

module.exports = function (app) {
  app.get("/one", function () {});
  app.post("/one", function () {});
};

Api

The module exports only one method registerRoutes(server, options) The server argument is your server or application on restify/express The options argument can have two properties.

options.path

This is mandatory and if not passed it should throw an Error.

options.pattern

You can use this property to specify a pattern to search for a file inside the module to require. This is useful if you don't want to use an index.js file in each module or if you want to give use for something different.

Ex: given you have the following module.

|_cars
  |_cars.routes.js
  |_handlers.js
  |_models
  | |_cars.js
  |_views
    |_list.ejs

Your options.pattern should be [folder].routes.js The [folder] token is the only one accepted in the pattern and will be replaced by the folder name at the root of the module.