chore(build): bumping to version 0.11.0-beta.1

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Sass.js Changelog
 
+## 0.11.0-beta.1 (February 6th 2018) ##
+
+* switching from ASM to WASM - ([Issue #74](https://github.com/medialize/sass.js/issues/74))
+
 ## 0.10.9 (February 6th 2018) ##
 
 * upgrading to [libsass 3.4.9](https://github.com/sass/libsass/releases/tag/3.4.9)

README.md

@@ -4,9 +4,12 @@ Sass parser in JavaScript. Have a look at the [Interactive Playground](http://sa
 
 This is a convenience API for [emscripted](https://github.com/kripken/emscripten) [libsass](https://github.com/sass/libsass) (at [v3.4.9](https://github.com/sass/libsass/releases/tag/3.4.9)). If you're looking to run Sass in node, you're probably looking for [node-sass](https://github.com/sass/node-sass). Sass.js and node-sass should generate the same results.
 
-A fair warning: minified the worker weighs 3.4MB, gzipped it's still 740KB. If you're on NodeJS, please use the (considerably faster) [node-sass](https://github.com/andrew/node-sass) instead.
 
-You may also be interested in giving [Dart Sass](https://github.com/sass/dart-sass) a shot.
+## Warning
+
+The total size of *gzipped* content is ~600KB (~2KB sass.js, ~80KB sass.worker.js, ~520KB libsass.wasm). Without gzip it's ~6KB sass.js, ~360KB sass.worker.js, ~1.7MB libsass.wasm.
+
+If you're on NodeJS, please use the (considerably faster) [node-sass](https://github.com/andrew/node-sass) instead. You may also be interested in giving [Dart Sass](https://github.com/sass/dart-sass) a shot.
 
 
 ## Documentation

docs/getting-started.md

@@ -6,6 +6,7 @@ Sass.js aims to run in all environments. To achieve that, it's provided in indiv
 * `dist/sass.worker.js`: The emscripted libsass loaded by `dist/sass.js` and the [Web Worker](https://developer.mozilla.org/en/docs/Web/API/Worker) utilities.
 * `dist/sass.sync.js`: The consumable API and emscripted libsass for running the compiler in the main thread. Use this only in environments not supporting Web Workers (e.g. Node, Rhino, Nashorn).
 * `dist/sass.node.js`: A convenience API around `dist/sass.sync.js` to compile directly from the file system.
+* `dist/libsass.wasm`: To WebAssembly compiled libsass, loaded by and relative to `dist/sass.worker.js`, `dist/sass.sync.js` and `dist/sass.node.js`.
 * `dist/file-size.js`: *(meta)* A file listing the sizes of the compiled files.
 * `dist/versions.js`: *(meta)* A file listing the versions of Sass.js, libsass and emscripten.
 
@@ -26,7 +27,7 @@ The regular way of running Sass.js in the browser is by using the Web Worker (se
 
 ### Using Sass.js with a module loader
 
-If you load `sass.js` by other means than then `<script>` example above, it cannot find the URL of `dist/sass.worker.js` by itself. In this case you need to tell Sass where to find the worker first:
+If you load `sass.js` by other means than then `<script>` example above, it cannot find the URL of `dist/sass.worker.js` (and `dist/libsass.wasm`) by itself. In this case you need to tell Sass where to find the worker first:
 
 ```js
 define(function defineSassModule(require) {
@@ -63,7 +64,7 @@ It is possible - but *not recommended* to use Sass.js in the main EventLoop by l
 </script>
 ```
 
-The synchronous API does not need to be told where to find the worker (using `Sass.setWorkerUrl()`) because everything is included in one file.
+The synchronous API does not need to be told where to find the worker (using `Sass.setWorkerUrl()`), but it will expect the file `libsass.wasm` next to `sass.sync.js` - meaning these two files *must* remain in the same directory.
 
 
 ## Using Sass.js in Node (and Rhino, Nashorn, …)

package.json

@@ -1,6 +1,6 @@
 {
   "name": "sass.js",
-  "version": "0.10.9",
+  "version": "0.11.0-beta.1",
   "libsass": "3.4.9",
   "title": "Sass.js - API for emscripted libsass",
   "description": "Sass.js is a convenience API for the JavaScript libsass (compiled with Emscripten)",