option to use old logger behavior

[RayGuo-ergou]

Feature Request

Hi I saw the logger behavior changed from an utility that check the environment, if the environment is product no message logger to just javascript console.*.

It makes sense for error and warning but for debug/log I would rather not having them logged in production for example: https://github.com/wxt-dev/wxt/blob/main/packages/storage/src/index.ts#L406-L409, in production I don't want to have this logged as it might be used in content scripts, and some of my settings are secret which I don't want to take the risk to expose to the website that my content script runs on.

What do you think to revert the old log behaviors only for debug (perhaps log also ?). Of course logs in the dev server etc will remind the same.

It might not be a big issue, but for example sentry will overrid the console.* based on websites owners config.

Is your feature request related to a bug?

"N/A"

What are the alternatives?

I am doing a work around at the moment like

export const settingsStorage = (() => {
  const debug = console.debug;
  if (import.meta.env.PROD) {
    console.debug = () => {};
  }
  const store = storage.defineItem<Settings>(SETTINGS_STORAGE_ITEM_KEY, {
    version: 2,
    init: () => defaultSettings,
    migrations: {
      2: (setting: SettingsV1): SettingsV2 => {
        return defu(setting, defaultSettingsV2);
      },
    },
  });
  return store;
})();

Additional context

[aklinker1]

Oh, woops, yes, we should clean that up. I also saw that there's one more console.log that got left in that file as well.

I can disable the logs in production

[RayGuo-ergou]

were these debug statement for your development🤔, now I am more thinking can completely remove the console log/debug, if the user want to know if a migration is done, can check the devtools. Only emit errors if the operation is unsuccessful.