bug: Could not find player for VM-CONTROLS

[jqueryisamonad]

Bug Report

Vime version:

5.0.33

Provider:

• [ ] Audio
• [x] Video
• [ ] HLS
• [ ] DASH
• [ ] YouTube
• [ ] Vimeo
• [ ] Dailymotion

Current behavior:

I try to run the React example from the documentation and get an error Could not find player for VM-CONTROLS

import React from "react";
import { Player, Video, DefaultUi, DefaultControls } from "@vime/react";

function App() {
  return (
    <Player>
      <Video crossOrigin="" poster="https://media.vimejs.com/poster.png">
        <source data-src="https://media.vimejs.com/720p.mp4" type="video/mp4" />
      </Video>
      <DefaultUi noControls>
        <DefaultControls />
      </DefaultUi>
    </Player>
  );
}

export default App;

Expected behavior:

It should work, I think

Steps to reproduce:

https://codesandbox.io/s/blue-wood-qqsy9

[T-Damer]

Yup, I have many errors in the console too:

[pateljoel]

I get these errors as well, very annoying. @mihar-22 do you know why this happens?

@jqueryisamonad Did you manage to get around this??

[jqueryisamonad]

@pateljoel no 🙃

[mihar-22]

This is a tricky bug, spent a little bit on it today and it seems to have to do with either HMR, when components are being defined or specifically the React integration. It doesn't happen with other packages, and it doesn't happen when using Vite. Until I can uncover more unforunately I can only recommended a full page reload when using Webpack, otherwise you can try out Vite and see how that goes.

[T-Damer]

Until I can uncover more unforunately I can only recommended a full page reload when using Webpack, otherwise you can try out Vite and see how that goes.

I am using Vite, but it still throws those errors, also Vite says, that it can't analyze dynamic import in one place, but I think it's another issue :)

[RaulPROP]

This also happens some times using Angular

[pooledge]

And Svelte

[FluorescentHallucinogen]

I have a very similar floating error Could not find player for VM-FILE while starting playing the HLS video stream. I've found that reloading the page helps reproduce or get rid of this bug.