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 🙏

© 2026 – Pkg Stats / Ryan Hefner

nodester-tools

v0.0.31

Published

Toolkit to help you with the nodester application development.

Readme

nodester tools

NPM version License

Toolkit to help you with the nodester application development.

Installation

Install with NPM

npm install -D nodester-tools

Usage

  1. Ensure your project has a file named nodester.config.js with the following content:
const Path = require('path');
const rootDir = process.cwd();

module.exports = {
  paths: {
    controllers: Path.join(rootDir, 'src/app/controllers'),
    facades:     Path.join(rootDir, 'src/app/facades'),
    filters:     Path.join(rootDir, 'src/app/filters'),
    models:      Path.join(rootDir, 'src/db/models'),
    providers:   Path.join(rootDir, 'src/app/providers'),
  }
}

controllers, facades, models, filters, providers are absolute paths to the corresponding directories in your project.

  1. Add nodester-tools to your npm scripts:
{
    ...
    "scripts": {
        ...
        "tools:generate": "nodester-tools -g",
    },
    "devDependencies": {
        "nodester-tools": "^0.0.3",
    },
    ...
}
  1. Call the neccessary generation command:

model:

Will create:

  • Model (if does not exist)
  • Facade (if does not exist)
  • Controller (if does not exist)
npm run tools:generate model <Model Name/>

filter:

When you are generating a filter, provide a Role argument

  • It will ensure a proper structure of your /filters directory
  • For example, if a role is admin, all the filters will be placed in /filters/<Model Name>/admin
npm run tools:generate filter <Model Name/> <Role/>

provider:

npm run tools:generate provider <Provider Name/>

License

MIT

Copyright

Copyright 2025-present Mark Khramko