Use console.context() for logging in Optimization Detective and export console logging functions to extensions

[westonruter]

I just learned about console.context() via https://devtoolstips.org/tips/en/create-contextual-console-loggers/

This can be used to filter messages by the context via the context: operator in the filter search box.

We could create info, warn, and log, error functions which we expose to the client-side extensions' initialize() and finalize() functions as well. Maybe these functions could automatically take into account the value of isDebug coming from WP_DEBUG in PHP, so that they automatically no-op when called. That would avoid the need to wrap calls in if ( isDebug ) { ... } all the time in extensions.

[ShyamGadde]

I noticed that console.context() is currently "an experiment in Chromium-based browsers only" according to the article you linked. This might cause errors in Firefox, Safari, and other non-Chromium browsers.

Would it make sense to implement simple feature detection before using it? Maybe something like:

function createLogger(...) {
    ...
    if (typeof console.context === 'function') {
        // Use console.context
    } else {
        // Fall back to regular console with prefixed messages
    }
    ...
}

This way we could still benefit from context in supported browsers.