I just have a tiny comment: you seem to have quite a few console logs left in the code (for debugging reasosns perhaps?), but it would look nicer if you could remove them. :)
I've wondered about this myself. There are times when I debug with console.log/.error during the dev cycle with potentially sensitive data that I would definitely remove before deploying. There are other times when I have output that just kind of lets me know where things are during execution where I've had the internal discussion of leaving them in or not. I usually lean on removing them all. However, I've had the console open on several large sites, and they are constantly filing up the console with output. It seems like it is mainly the 3rd-party libraries that sites include. Even Amazon's home page outputs content to the console.
<sidebar>
However, it is oddly satisfying for me to see the console full of warnings from Firefox of 'Request to access cookie was blocked' or 'Loading failed for the <script> with source googleadservices or doubleclick' type of messages.
