Allow user to control console

[MattShrider]

I currently intentionally have some providers as optional, so I often get console warnings from constate about the provider not being provided.

    if (isDev && value === NO_PROVIDER) {
      // eslint-disable-next-line no-console
      console.warn("[constate] Component not wrapped within a Provider.");
    }

I would like to hide them for my use-case. I'd recommend the feature be "fixed" by allowing the user to add their own console object, then it would be up to the user to filter this specific message.

import constate, { useConsole } from 'constate';
import log from 'loglevel';

const constateLogger= log.getLogger('constate');
constateLogger.setLevel(log.levels.ERROR);
useConsole(constateLogger)

const [Provider, hook] = constate(.....);

[aspirisen]

Hi, any updates on optional providers? I think it is often case when you have no providers.

[hiSandog]

Injecting an entire console object is a broad escape hatch for one semantic choice. An explicit optional/warnIfMissing option or onMissingProvider hook would document intent, preserve the helpful default warning, and let tests assert behavior without global logging mocks. The hook should run once per relevant context/component path rather than on every render to avoid noisy custom handling.