This is the weirdest glitch I've found in my entire existence.
If you add a <div id="process"> to the DOM, it breaks.
The problem is that Yaku checks for window.process, which seems to be defined in some browsers as $("#process"). Yaku then tries to use process.nextTick, which of course doesn't exist.
This doesn't happen in all browsers; not sure why.
This is the weirdest glitch I've found in my entire existence.
If you add a
<div id="process">
to the DOM, it breaks.The problem is that Yaku checks for
window.process
, which seems to be defined in some browsers as$("#process")
. Yaku then tries to useprocess.nextTick
, which of course doesn't exist.This doesn't happen in all browsers; not sure why.