Guaranteed way for getting a Promise. Always native Promise if available, otherwise looks for common promise libraries and loads which is installed. Allows registering custom Promise implementation in node < 0.12 versions
npm install native-or-another> Guaranteed way for getting a Promise. Always native Promise if available, otherwise looks for common promise libraries and loads which is installed. Allows registering custom Promise implementation in node < 0.12 versions
[![code climate][codeclimate-img]][codeclimate-url]
[![code style][standard-img]][standard-url]
[![linux build][travis-img]][travis-url]
[![windows build][appveyor-img]][appveyor-url]
[![code coverage][coverage-img]][coverage-url]
[![dependency status][david-img]][david-url]
[![paypal donate][paypalme-img]][paypalme-url]
_Pretty much like [any-promise][], but works a bit different & better._
> Let your library support any ES 2015 (ES6) compatible Promise and leave the
choice to application authors. The application can optionally register its preferred
Promise implementation and it will be exported when requiring any-promise from library code.
–– [any-promise][]
If no preference is registered, always defaults to native Promise,
using [native-promise][] detection. It defaults to global Promise for
newer Node.js >= 0.12 versions. The browser version defaults
to the window Promise, so polyfill or register as necessary.
_(TOC generated by verb using markdown-toc)_
```
$ npm install native-or-another --save
or install using yarn
``
$ yarn add native-or-another
Examples assumes that they are ran in older node versions, meaning < 0.12, be aware of that!
Use it as any other Promise. It will give you native Promise always,
until node < 0.12 - in that case it will try to load one of the common promise libraries,
otherwise it will throw with a useful message to signal your users to install
some of these promise implementations or register other one.
`js
const Promise = require('native-or-another')
const promise = new Promise((resolve, reject) => {
resolve(123)
})
promise.then((res) => console.log('foo:', res))
`
You can .register() a custom Promise which will be used by the main export.
That function also returns that Promise. If no arguments are passed, it will try to load some
of the common promise libraries, again.
`js
const register = require('native-or-another/register')
const MyCustomPromise = () => 444
register({ Promise: MyCustomPromise })
const Promize = require('native-or-another')
// loads MyCustomPromise
const res = Promize()
console.log(res) // => 444
// but also adds it to global scope
const res = Promise()
console.log(res) // => 444
// but also adds it to global.Promise
const res = global.Promise()
console.log(res) // => 444
`
Notice that it adds the promise to global scope and global, if you don't want that behaviour.register
you should disable it through passing an option to function, like { global: false }.
`js
const register = require('native-or-another/register')
const Promize = register({ global: false })
console.log(Promize) // => function
console.log(Promise) // => undefined
console.log(global.Promise) // => undefined
`
This is exactly how require('native-or-another') works!
Node.js versions prior to v0.12 may have contained buggy versions of the global Promise. Promise
For this reason, the global is not loaded automatically for these old versions. native-or-another
If using in Node.js versions < v0.12, the user should register a
desired implementation.
If an implementation is not registered, native-or-another will attempt to discover Promise
an installed implementation. If no implementation can be found, an error require('native-or-another')
will be thrown on . While the auto-discovery usually avoids errors,
it is non-deterministic. It is recommended that the user always register a preferred
implementation for older Node.js versions.
This auto-discovery is only available for Node.js versions before v0.12. v0.12
Any newer versions (includeing ) will always default to the global Promise implementation.
> Adapted from the [any-promise][] readme.
or falsey value if not available. | Promise or falsey value if not available."" class="text-primary hover:underline" target="_blank" rel="noopener noreferrer">homepage
- redolent: Simple promisify with sane defaults, works on node 0.10 if you provide custom Promise through options | homepage
- stacktrace-metadata: Modify given err object to be more useful - adds at, line, column, place and filename properties… more | err object to be more useful - adds at, line, column, place and filename properties and also cleans stack traces."" class="text-primary hover:underline" target="_blank" rel="noopener noreferrer">homepage
- try-catch-callback: try/catch block with a callback, used in [try-catch-core][]. Use it when you don't care about asyncness so… more | homepageContributing
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
``+ github/tunnckoCore
+ twitter/tunnckoCore
+ codementor/tunnckoCore
*
_This file was generated by verb-generate-readme, v0.4.3, on March 17, 2017._
_Project scaffolded using [charlike][] cli._
[always-done]: https://github.com/hybridables/always-done
[any-promise]: http://github.com/kevinbeaty/any-promise
[async-done]: https://github.com/gulpjs/async-done
[base]: https://github.com/node-base/base
[charlike]: https://github.com/tunnckocore/charlike
[commitizen]: https://github.com/commitizen/cz-cli
[dezalgo]: https://github.com/npm/dezalgo
[native-promise]: https://github.com/tunnckocore/native-promise
[once]: https://github.com/isaacs/once
[standard-version]: https://github.com/conventional-changelog/standard-version
[try-catch-core]: https://github.com/hybridables/try-catch-core
[verb-generate-readme]: https://github.com/verbose/verb-generate-readme
[verb]: https://github.com/verbose/verb
[license-url]: https://www.npmjs.com/package/native-or-another
[license-img]: https://img.shields.io/npm/l/native-or-another.svg
[downloads-url]: https://www.npmjs.com/package/native-or-another
[downloads-img]: https://img.shields.io/npm/dt/native-or-another.svg
[codeclimate-url]: https://codeclimate.com/github/tunnckoCore/native-or-another
[codeclimate-img]: https://img.shields.io/codeclimate/github/tunnckoCore/native-or-another.svg
[travis-url]: https://travis-ci.org/tunnckoCore/native-or-another
[travis-img]: https://img.shields.io/travis/tunnckoCore/native-or-another/master.svg?label=linux
[appveyor-url]: https://ci.appveyor.com/project/tunnckoCore/native-or-another
[appveyor-img]: https://img.shields.io/appveyor/ci/tunnckoCore/native-or-another/master.svg?label=windows
[coverage-url]: https://codecov.io/gh/tunnckoCore/native-or-another
[coverage-img]: https://img.shields.io/codecov/c/github/tunnckoCore/native-or-another/master.svg
[david-url]: https://david-dm.org/tunnckoCore/native-or-another
[david-img]: https://img.shields.io/david/tunnckoCore/native-or-another.svg
[standard-url]: https://github.com/feross/standard
[standard-img]: https://img.shields.io/badge/code%20style-standard-brightgreen.svg
[paypalme-url]: https://www.paypal.me/tunnckoCore
[paypalme-img]: https://img.shields.io/badge/paypal-donate-brightgreen.svg