Releasing features that rely on patching globals?

[HugoDF]

@KevinBatdorf raised a good comment about having a way to opt-in/out of the console.warn hijacking, see #140 (comment)

Since this hijacks console.warn, maybe we could make it opt in via a "experimental" setting? That feature is not wired up yet but after we get the settings chrome storage set up it should be trivial.

For this specific feature, when patching the console.warn the user loses the reference to the original code calling console.warn, maybe we should only start patching console.warn once someone goes to the "warnings" tab?

We could also have a general option like "opt in for all experimental features" and essentially have people beta testing features before they are available to everyone.

Vue.js devtools deal with this by having a "beta" release channel (they have a separate "devtools beta" extension)