bluebird - npm Package Compare versions
Comparing version 0.8.3-1 to 0.8.3-2
@@ -61,2 +61,4 @@ var astPasses = require("./ast_passes.js"); | ||
| var ZALGO_DEST = './zalgo.js'; | ||
| function writeFile( dest, content ) { | ||
@@ -232,3 +234,5 @@ grunt.file.write( dest, content ); | ||
| writeFile( BUILD_DEBUG_DEST, debugSrc ); | ||
| writeFile( ZALGO_DEST, syncSrc ); | ||
| if( shouldMinify ) { | ||
@@ -235,0 +239,0 @@ var ccDone = function( location, err, code ) { |
| { | ||
| "name": "bluebird", | ||
| "description": "Full featured Promises/A+ implementation with exceptionally good performance", | ||
| "version": "0.8.3-1", | ||
| "version": "0.8.3-2", | ||
| "keywords": [ | ||
@@ -6,0 +6,0 @@ "promise", |
@@ -36,3 +36,3 @@ <a href="http://promisesaplus.com/"> | ||
| var Promise = require("bluebird"); | ||
| ``` | ||
| ``` | ||
| ##Browsers | ||
@@ -152,4 +152,4 @@ | ||
| at Object.InjectedScript.evaluate (<anonymous>:450:21) | ||
| A better and more practical example of the differences can be seen in gorgikosev's [debuggability competition](https://github.com/spion/async-compare#debuggability). (for `--error` and `--throw`, promises don't actually need to handle `--athrow` since that is something someone using a promises would never do) | ||
@@ -178,6 +178,6 @@ | ||
| grunt test --run=233 --verbose | ||
| The reason for the unusual way of testing is because the majority of tests are from different libraries using different testing frameworks and because it takes forever to test sequentially. | ||
| ###Testing in browsers | ||
@@ -189,3 +189,3 @@ | ||
| setup | ||
| Then open the `index.html` in your browser. Requires bash (on windows the mingw32 that comes with git works fine too). | ||
@@ -204,3 +204,3 @@ | ||
| bench spion | ||
| While on the project root. Requires bash (on windows the mingw32 that comes with git works fine too). | ||
@@ -215,5 +215,9 @@ | ||
| While on the project root. Requires bash (on windows the mingw32 that comes with git works fine too). | ||
| ##What is the sync build? | ||
| You may now use sync build by: | ||
| var Promise = require("bluebird/zalgo"); | ||
| The sync build is provided to see how forced asynchronity affects benchmarks. It should not be used in real code due to the implied hazards. | ||
@@ -227,7 +231,7 @@ | ||
| async.invoke( this.fn, this, val ); | ||
| Appears as this in the sync build: | ||
| this.fn(val); | ||
| This should pressure the CPU slightly less and thus the sync build should perform better. Indeed it does, but only marginally. The biggest performance boosts are from writing efficient Javascript, not from compromising deternism. | ||
@@ -293,2 +297,2 @@ | ||
| OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
| THE SOFTWARE. | ||
| THE SOFTWARE. |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by52.76%
227214
- Number of package files
- increased by14.29%
8
- Lines of code
- increased by88.1%
5199
- Number of lines in readme file
- increased by1.75%
291