You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: