Player unusable after error at instantiation

[LoveIsGrief]

Maybe related to #165

Expected Behavior

The player should be able to call all its methods after instantiating a bad player, but their promises should all be caught.

Actual Behavior

Promises are never fullfilled.

Steps to Reproduce

Codepen

1. Create a new player with an invalid URL
2. Try to load a valid video

Possible source

callMethod in player.js. It only tries to do its stuff when the player is ready, but if it never started out ready, then it just won't do anything.

[mirague]

Also running into this problem, are there any known workarounds until this gets solved?

Edit: I can't even seem to create a new player instance, does it use some sort of global cache?

Edit 2: It seems the faulty players -are- in fact cached, even when it hits this "deadlock" failure state. See my comment below.

[mirague]

After looking into this I see that the player is cached inside a WeakMap, and returned if it already exists: https://github.com/vimeo/player.js/blob/master/src/player.js#L59

This poses a problem if you're trying to reuse the element inside for example React. Perhaps if the instantiation fails we should undo any created side-effects (in effect removing the cached element from the WeakMap)? Now users wanting to use Vimeo on a mounted React component are forced to use a hacky workaround to unmount the element from the DOM and re-insert it.

@luwes @bdougherty Thoughts?

[luwes]

When loading an invalid clip the ready promise will now reject and in turn all getters, setters and methods as well.