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

base-debug

v0.1.0

Published

Plugin for debugging your base application.

Downloads

2

Readme

base-debug NPM version Build Status

Plugin for debugging your base application.

Install

Install with npm:

$ npm i base-debug --save

Usage

To test-drive the plugin, add this to example.js (or just use the examples/example.js file in this project):

var debug = require('base-debug');
var Base = require('base');
var base = new Base();

base.use(debug('foo'));

var one = base.debug('one');
var two = base.debug('two');

one('this is one!');
two('this is two!');

Then, in the command line:

  • run DEBUG=base:* node example
  • then try DEBUG=base:one node example

(See the debug docs for more information about using debug on all platforms.)

Namespace

Inside your plugin, register the debug() plugin, passing the name of your plugin as the "namespace" to use:

// given you have a plugin named `base-foo`
function baseFoo(options) {
  return function(app) {
    app.use(debug('foo'));

    // then call the `app.debug` method
    var debug = app.debug();
    
    // then use it like this:
    debug('yelling abc: %s', 'ABC!');
    debug('yelling xyz: %s', 'XYZ!');
  }
}

When your plugin is registered, like this:

// Add your plugin
var base = new Base();
base.use(baseFoo());

and the DEBUG=base:foo command is used, you should see something like this in the terminal:

(See the debug docs for more information about using debug on all platforms.)

Sub-namespaces

Optionally use "sub-namespaces":

function baseFoo(options) {
  return function(app) {
    app.use(debug('foo'));
  
    // namespace `foo:one`
    var one = app.debug('one');

    // namespace `foo:two`
    var two = app.debug('two');
    
    // then use it like this:
    one('yelling abc: %s', 'ABC!');
    two('yelling xyz: %s', 'XYZ!');
  }
}

When your plugin is registered, like this:

// Add your plugin
var base = new Base();
base.use(baseFoo());

and the following commands are used:

  • DEBUG=base:foo:*, or
  • DEBUG=base:foo:one, or
  • DEBUG=base:foo:two

You should see something like this in the terminal:

(See the debug docs for more information about using debug on all platforms.)

Related projects

You might also be interested in these projects:

Running tests

Install dev dependencies:

$ npm i -d && npm test

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Author

Jon Schlinkert

License

Copyright © 2016 Jon Schlinkert Released under the MIT license.


This file was generated by verb on January 23, 2016.