Broken in IE11 due to calling console.warn.apply with null

[skatcat31]

Describe the bug
When transpiling to IE11, a console.warn statement is being called with the specific footprint of console.warn.apply(null, args) in the function warn

  function warn() {
    if (console && console.warn) {
      for (var _len = arguments.length, args = new Array(_len), _key = 0; _key < _len; _key++) {
        args[_key] = arguments[_key];
      }

      if (typeof args[0] === 'string') args[0] = `react-i18next:: ${args[0]}`;
      console.warn.apply(null, args);
    }
  }

Occurs in react-i18next version
from our package.json: "react-i18next": "^10.2.0"

To Reproduce
Steps to reproduce the behavior:

1. attempt to cause a warning in IE11

Expected behaviour
The script continues to execute

Actual Behavior
The script on IE11 fails due to incorrectly calling console.warn with a null context

Screenshots

OS (please complete the following information):

• Device: Windows 7
• Browser: IE11

Additional context
This cannot be recreated when dev tools are open due to the way dev tools wraps the console methods when injecting itself.

We have not checked for other console statement in the package

Any console statements called with apply with a context of null will fail.

This should be a simple fix of just replacing null in these apply statements with console