Shahrul Nizam Selamat

Just found out some of the spinners :before, :after is overlayed, not transparent

Taken back what I've written before; simple solution is to use [source-map-support](https://github.com/evanw/node-source-map-support) you write your test i.e ```javascript require('source-map-support').install() var test = require('tape-catch') test('virtual dom', function(t) { t.plan(1) t.equal(1, 2)...

You can clone [https://github.com/syarul/webpack-tape-run/tree/tape-run-v9](https://github.com/syarul/webpack-tape-run/tree/tape-run-v9) ``` npm install npm test ``` the test [file](https://github.com/syarul/webpack-tape-run/blob/tape-run-v9/test.js) ```javascript var test = require('tape') test('test success', function(t) { t.plan(2) t.equal(1, 1) t.equal('foo', 'bar') t.end() }) ```...

IMO, I think this similar to node.js on how to handle ```uncaughtException```. Where you need to feed the error back the tape-run, so that test will continue on failing ```js...

I believe the basic of this is to add document event listener for `touchstart`, `touchmove`, `touchend`, and `touchcancel`. So for example, it could be something similar like this ``` javascript...

I think this related to #356 issue, which avoid generating eot files. You might want to use previous version if you need the eot

the node engine has no issue generating the ```.eot```, might as well use that.

In my case on windows with `cygwin` you need either the `mingw64 openssl` devel installed first you can do with the installer `setup-x86_64.exe -q -P mingw64-x86_64-openssl` or if you want...

This is needed to fix the type imports if not there's no way to compile the TS build

Adding these ```guid``` will eventually add certain drag in the rendering pipeline. Also an efficient diffing will always beat spawning/search ids within a vtree/dom to do ```insertion/update/remove```