Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 400,000 packages pre-installed, including dush-no-chaining with all npm packages installed. Try it out:

var dushNoChaining = require("dush-no-chaining")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

dush-no-chaining v1.0.1

A plugin that removes the emitter methods chaining support for `dush`, `base`, `minibase` or anything based on them

dush-no-chaining NPM version mit license NPM monthly downloads npm total downloads

A plugin that removes the emitter methods chaining support for dush, base, minibase or anything based on them

code climate code style linux build windows build code coverage dependency status paypal donate

You might also be interested in dush.

Table of Contents

(TOC generated by verb using markdown-toc)


Install with npm

$ npm install dush-no-chaining --save

or install using yarn

$ yarn add dush-no-chaining


For more use-cases see the tests

const dushNoChaining = require('dush-no-chaining')



A plugin that removes support for emitter methods to be chainable. Basically, by default dush's methods (and most of other eventemitters) are chainable and some user don't like that feature that I need.

  • returns {Function}: A plugin function that can be passed to dush, minibase or base


const dush = require('dush')
const noChaining = require('dush-no-chaining')

const app = dush()

// by default they are chainable
  .on('foo', () => {})
  .once('bar', () => {})
  .emit('bar', 123)
  .emit('bar', 333)
  .emit('foo', 1)

// but when add this plugin
// they are not chainable
const emitter = dush().use(noChaining())

const noop = () => {}
const on = emitter.on('foo', noop)
console.log(on) // => undefined

const off ='foo', noop)
console.log(off) // => undefined

const once = emitter.once('bar', noop)
console.log(once) // => undefined

const emit = emitter.emit('bar', 123)
console.log(emit) // => undefined


  • always-done: Handle completion and errors with elegance! Support for streams, callbacks, promises, child processes, async/await and sync functions. A drop-in replacement… more | homepage
  • base: base is the foundation for creating modular, unit testable and highly pluggable node.js applications, starting with a handful of common… more | homepage
  • dush-methods: Plugin for dush and anything based on it. It adds helper .define and .delegate methods | homepage
  • dush-tap-report: A simple TAP report producer based on event system. A plugin for dush event emitter or anything based on it | homepage
  • dush: Microscopic & functional event emitter in ~260 bytes, extensible through plugins. | homepage
  • find-callsite: Finds the correct place where the stack trace was started, not the place where error was thrown | homepage
  • minibase-create-plugin: Utility for minibase and base that helps you create plugins | homepage
  • minibase: Minimalist alternative for Base. Build complex APIs with small units called plugins. Works well with most of the already existing… more | homepage
  • stacktrace-metadata: Modify given err object to be more useful - adds at, line, column, place and filename properties and also cleans… more | homepage
  • try-catch-core: Low-level package to handle completion and errors of sync or asynchronous functions, using once and dezalgo libs. Useful for and… more | homepage


Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards.
If you need some help and can spent some cash, feel free to contact me at too.

In short: If you want to contribute to that project, please follow these things

  1. Please DO NOT edit, and files. See "Building docs" section.
  2. Ensure anything is okey by installing the dependencies and run the tests. See "Running tests" section.
  3. Always use npm run commit to commit changes instead of git commit, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.
  4. Do NOT bump the version in package.json. For that we use npm run release, which is standard-version and follows Conventional Changelog idealogy.

Thanks a lot! :)

Building docs

Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb command like that

$ npm install verbose/verb#dev verb-generate-readme --global && verb

Please don't edit the README directly. Any changes to the readme must be made in

Running tests

Clone repository and run the following in that cloned directory

$ npm install && npm test


Charlike Mike Reagent


Copyright © 2017, Charlike Mike Reagent. Released under the MIT License.

This file was generated by verb-generate-readme, v0.4.3, on March 22, 2017.
Project scaffolded using charlike cli.


RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free