FredericH
On one hand it add a few bytes on the lib, on the other side, it adds more code and hassle on the client's code, making the overall bundle size...
At the moment, passing a null or an undefined property value results in a crash, IMHO, this is not acceptable as a library must be bullet proof whatever the input.
By crash, I meant a blank screen, which happened for both #39 and #40
The blank screen happens for these 2 use cases: ``` div({ a: undefined }) div(undefined) ``` The stack trace is: ``` van.js:54 Uncaught TypeError: Cannot convert undefined or null to...
A third way to get a blank screen in the following condition: ``` const inputState = van.state(undefined); and p({ id: inputState }) ```
Macosx, the code splitting example doesn't work either.
I've tried again with a fresh install and the issue is still present. Probably due to a recent node version: 8.4
fixed in v2.2.31
The dist build is now failing: ``` Error: ENAMETOOLONG: name too long, open '(function($fsx){ // moment/moment.js $fsx.f[0] = function(module,exports){ ; ```
uglify should be already installed? https://github.com/fuse-box/fuse-box-examples/blob/master/package.json#L28