vird

Proof. /** * This will save a change-set into the local storage. * This function ignores folder-level deletes and overwrites, * but those can't happen under the current rules anyhow....

Also I've found that up to 4 concurrent saveChanges calls was in progress when 5th started. if (fireCount > 0) { console.log("FIRE!!!", fireCount); } 

fix proposal https://github.com/vird/edge-core-js/commit/887b5bc310630622c7eb58cc7cbfff75f99a411d Note not MR yet, because I didn't get what flow errors means :-(

So. Right now workaround is using old node.js https://github.com/TooTallNate/ref/issues/125 Confirmed node versions: 10.18.0 11.15.0

N.b. should be compiled as `const b6 : bytes = Bytes.sub(1n, 2n, b0);` for cast to int function foo (const a : int ; const b : int) : int...

https://gist.github.com/vird/e40e12a9df566a9f1434a7580ca11dbb ```js function(str) { var arr, idx, str_bin, v, _i, _len; str_bin = atob(str); arr = new Uint8Array(str_bin.length); for (idx = _i = 0, _len = str_bin.length; _i < _len;...