Release v0.5.2

README.md

@@ -2,23 +2,26 @@
 
 [![Build Status](https://travis-ci.org/v8/web-tooling-benchmark.svg?branch=master)](https://travis-ci.org/v8/web-tooling-benchmark) [![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier)
 
-This is a benchmark suite designed to measure the JavaScript related
-workloads commonly used by Web Developers nowadays, for example the
+This is a benchmark suite designed to measure the JavaScript-related
+workloads commonly used by web developers, such as the
 core workloads in popular tools like [Babel](https://github.com/babel/babel)
-or [TypeScript](https://github.com/Microsoft/TypeScript). It's the
-explicit goal to measure **only** the JavaScript performance aspect,
-which is affected by the JavaScript engine, and not measure I/O or
-other unrelated aspects.
+or [TypeScript](https://github.com/Microsoft/TypeScript). The goal is to measure **only** the
+JavaScript performance aspect (which is affected by the JavaScript engine) and not measure I/O
+or other unrelated aspects.
 
 See the [in-depth
 analysis](https://github.com/v8/web-tooling-benchmark/blob/master/docs/in-depth.md)
 for a detailed description of the tests included in this benchmark suite.
 
-The latest browser version of the benchmark is available at <https://v8.github.io/web-tooling-benchmark/>.
+The latest browser version of the benchmark is available at
+<https://v8.github.io/web-tooling-benchmark/>.
 
 ## Support
 
-The Web Tooling Benchmark supports the latest [active LTS](https://github.com/nodejs/Release#release-schedule) version of Node.js. To see the supported Node.js versions of the current version of the benchmark, see [the `node_js` section of our CI configuration](https://github.com/v8/web-tooling-benchmark/blob/master/.travis.yml).
+The Web Tooling Benchmark supports the latest [active
+LTS](https://github.com/nodejs/Release#release-schedule) version of Node.js. To see the supported
+Node.js versions of the current version of the benchmark, see [the `node_js` section of our CI
+configuration](https://github.com/v8/web-tooling-benchmark/blob/master/.travis.yml).
 
 ## Building
 
@@ -47,28 +50,28 @@ i.e. like this:
 
 ```
 $ node dist/cli.js
-Running Web Tooling Benchmark v0.5.1…
+Running Web Tooling Benchmark v0.5.2…
 -------------------------------------
-         acorn:  6.11 runs/s
-         babel:  5.59 runs/s
-  babel-minify:  6.79 runs/s
-       babylon:  5.48 runs/s
-         buble:  3.31 runs/s
-          chai: 10.49 runs/s
-  coffeescript:  4.72 runs/s
-        espree:  3.44 runs/s
-       esprima:  4.27 runs/s
-        jshint:  6.38 runs/s
-         lebab:  5.76 runs/s
-       postcss:  4.35 runs/s
-       prepack:  5.07 runs/s
-      prettier:  4.36 runs/s
-    source-map:  6.66 runs/s
-        terser: 10.87 runs/s
-    typescript:  6.62 runs/s
-     uglify-js:  3.48 runs/s
+         acorn:  5.50 runs/s
+         babel:  6.10 runs/s
+  babel-minify:  9.13 runs/s
+       babylon:  8.00 runs/s
+         buble:  4.77 runs/s
+          chai: 14.47 runs/s
+  coffeescript:  5.62 runs/s
+        espree:  4.05 runs/s
+       esprima:  6.68 runs/s
+        jshint:  7.84 runs/s
+         lebab:  7.52 runs/s
+       postcss:  5.06 runs/s
+       prepack:  6.26 runs/s
+      prettier:  5.97 runs/s
+    source-map:  8.60 runs/s
+        terser: 16.40 runs/s
+    typescript: 10.04 runs/s
+     uglify-js:  3.81 runs/s
 -------------------------------------
-Geometric mean:  5.45 runs/s
+Geometric mean:  6.98 runs/s
 ```
 
 Or you open a web browser and point it to `dist/index.html`, or you can use one

package.json

@@ -1,7 +1,7 @@
 {
   "name": "web-tooling-benchmark",
   "description": "JavaScript benchmark for common web developer workloads",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "repository": "https://github.com/v8/web-tooling-benchmark",
   "main": "src/cli.js",
   "scripts": {