IE 11: Invalid calling object

[brianleipprandt]

I'm seeing a 'Invalid calling object' exception in IE 11 when calling jwtDecode with my token. Other browsers seem to all be working.

It looks like this may be related to not binding window.atob in lib/atob.js when the polyfill isn't used.

Stack:

{exception} :
  description: "Invalid calling object",
  message: "Invalid calling object",
  name: "TypeError",
  number: -2147418113,
  stack "TypeError: Invalid calling object\n   at b64DecodeUnicode (eval code:4:3)\n   at module.exports (eval code:29:5)\n   at module.exports (eval code:10:3)\n   at updateAuthToken (eval code:34:3)\n   at auth (eval code:96:7)\n   at combination (eval code:117:7)\n   at dispatch (eval code:179:7)\n   at Anonymous function (eval code:208:13)\n   at Anonymous function (eval code:14:9)\n   at Anonymous function (eval code:140:9)"

Manual checks via debugger in b64DecodeUnicode:

window.atob('test')
"µë-"
atob('test')
Invalid calling object
atob
function atob() { [native code] }
atob === window.atob
True
var bound_atob = window.atob.bind(window);
undefined
bound_atob('test')
"µë-"

[mikecousins]

As a heads-up, I couldn't wait any longer on this being fixed so I forked it and made a new version with this fix in.

https://www.npmjs.com/package/jwt-decode-ie

I think I will deprecate it after this gets fixed here though.