Giter Club home page Giter Club logo

dush-no-chaining's Introduction

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

Install with npm

$ npm install dush-no-chaining --save

or install using yarn

$ yarn add dush-no-chaining

Usage

For more use-cases see the tests

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

API

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

Example

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

const app = dush()

// by default they are chainable
app
  .on('foo', () => {})
  .once('bar', () => {})
  .emit('bar', 123)
  .off('foo')
  .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 = emitter.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

Related

  • 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

Contributing

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 CodeMentor.io too.

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

  1. Please DO NOT edit README.md, CHANGELOG.md and .verb.md 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 .verb.md.

Running tests

Clone repository and run the following in that cloned directory

$ npm install && npm test

Author

Charlike Mike Reagent

License

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.

dush-no-chaining's People

Contributors

greenkeeper[bot] avatar tunnckocore avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar

dush-no-chaining's Issues

An in-range update of dush is breaking the build 🚨

Version 3.0.5 of dush just got published.

Branch Build failing 🚨
Dependency dush
Current Version 3.0.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As dush is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • ci/circleci CircleCI is running your tests Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 4 failing dependencies. Details

Commits

The new version differs by 8 commits.

  • 7c403dd chore(release): 3.0.5
  • c7162ce fix(update): add eslintrc and format the codebase
  • f3f75a8 chore(package): update standard to version 10.0.1
  • 39140c7 Update rollup-plugin-uglify to version 2.0.1 🚀 (#16)
  • eae6639 Merge branch 'master' into greenkeeper-rollup-plugin-uglify-2.0.1
  • ba113a8 Merge pull request #14 from tunnckoCore/greenkeeper-standard-10.0.2
  • 4d8869c chore(package): update rollup-plugin-uglify to version 2.0.1
  • 74f9cac chore(package): update standard to version 10.0.2

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of dush is breaking the build 🚨

Version 3.0.3 of dush just got published.

Branch Build failing 🚨
Dependency dush
Current Version 3.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As dush is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • ci/circleci CircleCI is running your tests Details

  • continuous-integration/travis-ci/push The Travis CI build is in progress Details

  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • bitHound - Code No failing files. Details

  • bitHound - Dependencies 3 failing dependencies. Details

Commits

The new version differs by 2 commits .

  • 81d4018 chore(release): 3.0.3
  • c6972dd fix(readme): update plugins list and github tag badge link

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of dush is breaking the build 🚨

Version 3.0.4 of dush just got published.

Branch Build failing 🚨
Dependency dush
Current Version 3.0.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As dush is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • ci/circleci Your tests passed on CircleCI! Details

  • continuous-integration/travis-ci/push The Travis CI build passed Details

  • continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • 043da3f chore(release): 3.0.4
  • 958ed95 fix(.use): allow passing options as second argument
  • 630518e chore(package): GreenKeeper enabled, update all dependencies (#11)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of standard-version is breaking the build 🚨

Version 4.2.0 of standard-version just got published.

Branch Build failing 🚨
Dependency standard-version
Current Version 4.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As standard-version is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • bitHound - Dependencies 4 failing dependencies. Details
  • bitHound - Code No failing files. Details
  • ci/circleci Your tests passed on CircleCI! Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 2 commits.

  • 2790e08 chore(release): 4.2.0
  • bc0fc53 feat: add support for package-lock.json (#190)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.2 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.3.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details,- ✅ bitHound - Code No failing files. Details,- ❌ bitHound - Dependencies 3 failing dependencies. Details,- ✅ ci/circleci Your tests passed on CircleCI! Details,- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details

Commits

The new version differs by 2 commits0.

  • e062a86 chore(release): 10.3.2
  • 213206f fix: we should not create a cache folder if cache is false (#567)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.2.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.1.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits .

  • 455619f chore(release): 10.2.0
  • 95cc09a feat: upgrade to version of yargs with extend support (#541)
  • 43535f9 chore: explicit update of istanbuljs dependencies (#535)
  • 98ebdff feat: allow babel cache to be enabled (#517)
  • 50adde4 feat: exclude the coverage/ folder by default 🚀 (#502)
  • 6a59834 chore(package): update tap to version 10.0.0 (#507)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of dush is breaking the build 🚨

Version 3.0.1 of dush just got published.

Branch Build failing 🚨
Dependency dush
Current Version 3.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As dush is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • ci/circleci CircleCI is running your tests Details

  • continuous-integration/travis-ci/push The Travis CI build is in progress Details

  • continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • bitHound - Code No failing files. Details

  • bitHound - Dependencies 3 failing dependencies. Details

Commits

The new version differs by 7 commits .

  • 62750cd chore(release): 3.0.1
  • 5b1fa43 fix(readme): add list of plugins
  • af1bc04 fix(readme): include ToC
  • 671d2eb docs(readme): tweaks
  • e9321a2 fix(readme): update boilerplate
  • 17bd948 fix(ci): move to CircleCI, instead of TravisCI
  • 7d6c4e2 fix(index): make detection "sourceString" more private

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 10.3.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.2.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/tunnckoCore/dush-no-chaining/build/1.0.34),- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/tunnckoCore/dush-no-chaining/builds/227092404?utm_source=github_status&utm_medium=notification),- ❌ **bitHound - Dependencies** 3 failing dependencies. [Details](https://www.bithound.io/github/tunnckoCore/dush-no-chaining/883371f7d7691f8219d2004dbe441f842226176b/dependencies/npm#filter-failing-dep),- ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/tunnckoCore/dush-no-chaining/883371f7d7691f8219d2004dbe441f842226176b/files?status=passing),- ❌ **ci/circleci** CircleCI is running your tests [Details](https://circleci.com/gh/tunnckoCore/dush-no-chaining/14?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

Commits

The new version differs by 4 commits ahead by 4, behind by 2.

  • 55e826d chore(release): 10.3.0
  • 89dc7a6 chore: explicit update of istanbul dependnecies (#562)
  • 1887d1c feat: add support for --no-clean, to disable deleting raw coverage output (#558)
  • ff73b18 fix: source-maps were not being cached in the parent process when --all was being used (#556)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.