foo

CHANGELOG.md

@@ -1,5 +1,16 @@
 
 
+## v3.0.0 - 2015-09-29
+- Release v3.0.0 / npm@v3.0.0
+- change prurpose of the library
+- refactor and update boilerplate
+
+Basically, because `native-or-bluebird` always first try to use `bluebird` and then fallbacks to native Promise if available. So you don't have ability to get Promise or to provide different promise module than `bluebird`.
+
+So `native-or-another` is here to help and always will give you Promise, no matter what enviroment you use - 0.10, 0.11, 0.12, iojs or latest v4. Always will try to give you native Promsie first, otherwise will give you `bluebird` promise, but only if you don't give another promise module like `q` or `promise` or what you want.
+
+You also can check what promise you use. If you use custom promise `Promise` module, the constructor will have property called `__customPromise` with `true` value. If you use `Bluebird` you will have property on the constructor `__bluebirdPromise` and again with `true` value. Otherwise they won't exist.
+
 ## v2.0.0 - 2014-12-21
 - Release v2.0.0 / npm@v2.0.0
 - change the purpose of library

package.json

@@ -1,6 +1,6 @@
 {
   "name": "native-or-another",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "Always will expose native `Promise` if available, otherwise `Bluebird` but only if you don't give another promise module like `q` or `promise` or what you want.",
   "repository": "tunnckoCore/native-or-another",
   "author": "Charlike Mike Reagent <@tunnckoCore> (http://www.tunnckocore.tk)",