Adding CDN player.js to a page which already has require.js on it will fail

Expected Behavior

player.js is instantiated without any problems and videos play happily.

Actual Behavior

The define functions clash with the already instantiated RequireJS.

Steps to Reproduce

1. Load a copy of RequireJS. Having it actual resolve dependencies is unnecessary for issue reproduction.
2. Later, include the CDN link to player.js in a script tag. This is done by a number of external libraries.
3. The summoned video will not play.

I have a quickly knocked-together pen: http://codepen.io/jodi/pen/qqbXxw

Apologies for all the script tags, it’s just for easy toggling so you can see the effects each setting/script has.

My suggestion is to provide either a separate player.iife.js or something for including via a script tag. Alternatively, maybe provide the iife version by default. Maybe I don’t have enough knowledge, but I don’t think the user would need the AMD or CommonJS module syntaxes when accessing it via a CDN.

[JodiWarren]

@bdougherty Not to my knowledge. UMD makes sense in most circumstances. I’m sure there’s a better solution than what I’ve proposed, but I couldn’t find one.

I’ve now had to fix a few Magento 2 sites which had included player.js via the CDN, so I’m assuming there are more of them out there too. My method has been to generate a custom build of player.js with the Rollup format option set to iife and use that instead.

Perhaps just a note in the documentation suggesting doing the above would suffice!

[BB-000]

Still struggling to get this to work with require.js & Magento 2…

Uncaught TypeError: Vimeo.Player is not a constructor

requirejs-config.js:

var config = {
  map: {
    '*': {
      'vimeo': 'js/vendor/vimeo',
    }
  }
};

js file:

require(['jquery', 'vimeo'], function ($, Vimeo) {
    player1 = new Vimeo.Player('vid-1', { id: 0101010 });
    player1.play();
});

Seems correct to me. Do I need to change the player.js file?