Function name class when using Dexie and JSzip on same page due to setImmediate

[davidhill001]

When including both Dexie (with observable and syncable modules) and the JSZip library, the sync callback within Dexie seems to switch over to a function within the JSZip library which I believe causes the message "Sync Status changed: ERROR" to show in the console.

When looking at the console trace, it seems that it is pulling the setImmediate function from the JSzip library.

Is there anything that can be done to avoid this? I am including JSZip as it is required by DataTables.

Here is the setImmediate function from JSZip:

    function setImmediate(callback) {
      // Callback can either be a function or a string
      if (typeof callback !== "function") {
        callback = new Function("" + callback);
      }
      // Copy function arguments
      var args = new Array(arguments.length - 1);
      for (var i = 0; i < args.length; i++) {
          args[i] = arguments[i + 1];
      }
      // Store and register the task
      var task = { callback: callback, args: args };
      tasksByHandle[nextHandle] = task;
      registerImmediate(nextHandle);
      return nextHandle++;
    }

[dfahlander]

The old dexie-observable / dexie-syncable addons does use setImmediate in case it is present on the global object to fire off queue consumer. Probably JSzip puts its setImmediate onto the global object / window / self, making the addons pick it up. There's nothing we can do in the addons to avoid it, but if JSZip isn't dependent on setting it on the global objects, one way would be to delete setImmediate from the global object after importing JSZip (just speculations)