When using the player.js file on the CDN it should load the file correctly
Currently, there is a stack overflow exception that runs on IE11. This is caused by your use of the es6-collections in your player.js file. Just letting you know that according to the build, it is not being used and I built it out and pulled the dependency out and it ran correctly on browsers.
Run the CDN version of the player.js file in IE11 on Windows 8 and you will see an error like so:

Does this happen on the api demo page? If not, could you link to a page that reproduces the error on something like CodePen or JSFiddle?
es6-collections is only required to polyfill WeakMap in IE 8 and 9, which we support with this library.
I tested it with the demo page on IE 11 and it worked and worked in a JS Fiddle. I will look into finding a link to help reproduce it, sorry I don't have one handy.
Just chiming in to say that I have run into this same error - same steps to reproduce & all. @jovialgent thanks for pointing this out, and @bdougherty thanks for offering a sanity check.
@jovialgent Any updates on your end?
@warrenmcquinn Sadly no. I have been using a custom build of the library on my end that removed that dependency that was breaking my project. But, as mentioned above, that dependency is required for IE 8 & 9. If you need it to be backwards compatible, then you may need to find another option.
I couldn't reproduce this on my end. Is this still an issue @jovialgent @warrenmcquinn ?
We did some testing on on a real browser on IE 11 and couldn't reproduce.
Closing for now, please re-open if you see otherwise. thanks!
I get this same stack space problem with IE11 on Windows Server 2012 R2, and with IE11 on a recently upgraded Win 10 computer. No problem on a Win 8.1's IE11.
Also seemingly caused by es6-collections.
I get the same issue for IE11 on Win 10, Win 8.1 and Win 7.
I'm having the issue right now
same
Same. HELP!
Same issue here. Getting the "Out of stack space." error in all versions of IE but not in any other browser.
Does anyone have an URL where this is happening?
On the https://player.vimeo.com/api/demo page I can't seem to reproduce this.
For us this error was caused by having the map package of core-js on the page where we also load the vimeo player script. When I tried es6-map instead, the error disappeared.
We replaced the es6-collections polyfill with the weakmap-polyfill.
https://github.com/vimeo/player.js/releases/tag/v2.6.3