It’s quite well known that passing an object in JavaScript passes a memory reference.
It turns out when logging nested objects to the console in Chrome, Chrome logs the reference to any nested objects rather than taking a deep snapshot. Which can make debugging more difficult, to say the least.
2 responses to “Live objects in Chrome’s console.log”
@pwcc yeah, and it can be a bit annoying when trying to debug using console.log
@divinegod that’s how I got caught, had messed up an Ajax promise but console was showing it worked. Live & learn.