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.

@ShyamGadde yes, that makes sense. That being said, if this is experimental maybe it's too early to ship.

In the mean time, we could look at exporting log, info, warn, and error functions to the async initialize and finalize functions used by extensions which include the isDebug check by default.

This would eliminate the following code:

And if the functions included the isDebug checks by default, we could remove the conditions from:

And so on.

We can revisit console.context() when it becomes stable.