Neo-Async

Neo-Async is thought to be used as a drop-in replacement for Async, it almost fully covers its functionality and runs faster.

Benchmark is here!

Bluebird's benchmark is here!

Code Coverage

Installation

In a browser

<script src="async.min.js"></script>

In an AMD loader

require(['async'], function(async) {});

Promise and async/await

I recommend to use Aigle.

It is optimized for Promise handling and has almost the same functionality as neo-async.

Node.js

standard

$ npm install neo-async

var async = require('neo-async');

replacement

$ npm install neo-async
$ ln -s ./node_modules/neo-async ./node_modules/async

var async = require('async');

Bower

bower install neo-async

Feature

JSDoc

* not in Async

Collections

Control Flow

parallel
series
parallelLimit
tryEach
waterfall
angelFall *
angelfall -> angelFall *
whilst
doWhilst
until
doUntil
during
doDuring
forever
compose
seq
applyEach
applyEachSeries
queue
priorityQueue
cargo
auto
autoInject
retry
retryable
iterator
times
timesSeries
timesLimit
race

Mode

safe *
fast *

Benchmark

Benchmark: Async vs Neo-Async

How to check

$ git clone git@github.com:suguru03/async-benchmark.git
$ cd async-benchmark
$ npm install
$ node . // It might take more than one hour...

Environment

Ubuntu v12.04
Node.js v6.2.1
async v2.0.0-rc.6
neo-async v2.0.0-rc.1
benchmark v2.1.0
func-comparator v0.7.1

Result

Neo-Async is 1.27 ~ 10.7 times faster than Async.

The value is the ratio (Neo-Async/Async) of the average speed.

Collections

function	benchmark	func-comparator
each	3.71	2.54
eachSeries	2.14	1.90
eachLimit	2.14	1.88
eachOf	3.30	2.50
eachOfSeries	1.97	1.83
eachOfLimit	2.02	1.80
map	4.20	4.11
mapSeries	2.40	3.65
mapLimit	2.64	2.66
mapValues	5.71	5.32
mapValuesSeries	3.82	3.23
mapValuesLimit	3.10	2.38
filter	8.11	8.76
filterSeries	5.79	4.86
filterLimit	4.00	3.32
reject	9.47	9.52
rejectSeries	7.39	4.64
rejectLimit	4.54	3.49
detect	6.67	6.37
detectSeries	3.54	3.73
detectLimit	2.38	2.62
reduce	4.13	3.23
reduceRight	4.23	3.24
transform	5.30	5.17
sortBy	2.24	2.37
some	6.39	6.10
someSeries	5.37	4.66
someLimit	3.39	2.84
every	6.85	6.27
everySeries	4.53	3.90
everyLimit	3.36	2.75
concat	9.18	9.35
concatSeries	7.49	6.09

Control Flow

funciton	benchmark	func-comparator
parallel	7.54	5.45
series	3.29	2.41
waterfall	5.12	4.27
whilst	1.96	1.95
doWhilst	2.07	1.96
until	2.10	1.99
doUntil	1.98	2.04
during	10.7	7.09
doDuring	5.98	6.03
queue	1.83	1.75
priorityQueue	1.79	1.75
times	3.84	3.65
race	1.45	1.27
auto	3.23	3.50
retry	9.43	6.78

Keine Beschreibung

Struktur: c867e20322

Branches Tags

master
adminSystem
/
node_modules
/
postcss-convert-values


..
dist	11e3a9652a	first	vor 8 Jahren
node_modules	11e3a9652a	first	vor 8 Jahren
CHANGELOG.md	11e3a9652a	first	vor 8 Jahren
LICENSE-MIT	11e3a9652a	first	vor 8 Jahren
README.md	11e3a9652a	first	vor 8 Jahren
package.json	11e3a9652a	first	vor 8 Jahren

postcss-convert-values

Convert values with PostCSS (e.g. ms -> s)

Install

With npm do:

npm install postcss-convert-values --save

Example

This plugin reduces CSS size by converting values to use different units where possible; for example, 500ms can be represented as .5s. You can read more about these units in this article.

Input

h1 {
    font-size: 16px;
    width: 0em
}

Output

h1 {
    font-size: 1pc;
    width: 0
}

Note that this plugin only covers conversions for duration and absolute length values. For color conversions, use postcss-colormin.

API

convertValues([options])

options

length

Type: boolean Default: true

Pass false to disable conversion from px to other absolute length units, such as pc & pt & vice versa.

time

Type: boolean Default: true

Pass false to disable conversion from ms to s & vice versa.

angle

Type: boolean Default: true

Pass false to disable conversion from deg to turn & vice versa.

precision

Type: boolean|number Default: false

Specify any numeric value here to round px values to that many decimal places; for example, using {precision: 2} will round 6.66667px to 6.67px, and {precision: 0} will round it to 7px. Passing false (the default) will leave these values as is.

It is recommended for most use cases to set this option to 2.