DOM.js breaks console.log in p5js editor

[jht9629-nyu]

// https://editor.p5js.org/jht9629-nyu/sketches/VY-KQxJkA
// DOM.js console.log bug
// run this sketch and get error:
// "RangeError: Maximum call stack size exceeded"
// disable DOM.js include and console.log works
//

[jht9629-nyu]

Linked to p5js as issue:

• Using DOM.js library kills console.log processing/p5.js#7610
• Using DOM.js library kills console.log #7610

Logged as p5js editor issue:

processing/p5.js-web-editor#3386
Using DOM.js library kills console.log #3386

[dipamsen]

By using the chrome debugger and reading the sourcecode of DOM.js, this is what I found - due to DOM.js setting a new property on Object.prototype, it breaks some logic within core-js which polyfils Function.toString() for older browsers. Due to this, there is a stackoverflow within the core-js logic.

This is in fact one of the reasons why setting properties on Object.prototype is generally not encouraged. But in this case the issue can be fixed by setting the property as non enumerable, so that core-js does not see it when enumerating on properties of objects:

Object.defineProperty(Object.prototype, "binderSet", {
  value: ...,
  enumerable: false
});

• Object.defineProperty

[jht9629-nyu]

@dipamsen Thank you for detailed follow up