npm - @videojs/react - Versions diffs - 10.0.0-rc.2 → 10.0.0-rc.3 - Mend

@videojs/react 10.0.0-rc.2 → 10.0.0-rc.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (2117) hide show

package/docs/how-to/build-your-own-component.md DELETED Viewed

@@ -1,271 +0,0 @@
-# Build your own UI component
-Create custom player controls that read state, dispatch actions, and stay accessible.
-Custom components subscribe to player state and dispatch actions, like built-in controls.
-## You might not need a custom component
-Before building from scratch, check if an existing approach covers your use case:
-*   **Change what a control renders**: use the `render` prop on any built-in component. See [UI components](../concepts/ui-components.md).
-*   **Restyle a control**: use CSS custom properties and data attributes. See [UI components](../concepts/ui-components.md).
-*   **Rearrange or remove controls**: eject a skin and modify it. See [Customize skins](./customize-skins.md#eject-and-edit-a-skin).
-Build a custom component when you need new behavior, a new state display, or integration with an external system.
-## Use player state and actions
-Need access to player state or actions? You’ll want to familiarize yourself with [features](../concepts/features.md). Each feature exposes a set. Here are some features you might reach for first:
-State
-Actions
-Feature
-`paused`, `ended`
-`play()`, `pause()`
-[Playback](../reference/feature-playback.md)
-`currentTime`, `duration`
-`seek()`
-[Time](../reference/feature-time.md)
-`volume`, `muted`
-`setVolume()`, `toggleMuted()`
-[Volume](../reference/feature-volume.md)
-`fullscreen`
-`requestFullscreen()`, `exitFullscreen()`
-[Fullscreen](../reference/feature-fullscreen.md)
-Browse the full list in the **Features** section of the sidebar.
-Features for platform-dependent capabilities also expose one or more **availability** properties (`'available'`, `'unavailable'`, or `'unsupported'`) for hiding controls the platform does not support. See [Features](../concepts/features.md) for details.
-Access state and actions with [`usePlayer`](../reference/use-player.md):
-tsx
-```
-import { usePlayer } from '@videojs/react';
-// Subscribe to state — re-renders only when selected values change
-const paused = usePlayer((s) => s.paused);
-const currentTime = usePlayer((s) => s.currentTime);
-// Get the store for dispatching actions (does not subscribe)
-const store = usePlayer();
-await store.play();
-store.setVolume(0.5);
-store.seek(30);
-```
-## Place your component in the player
-Your component needs to be inside [`<Player>`](../reference/player.md) to access state. Place it inside [`<Container>`](../reference/player-container.md) if it should also participate in fullscreen and respond to user activity:
-tsx
-```
-import { Container } from '@videojs/react';
-<Player>
-  <Container>
-    <VideoSkin>
-      <Video src="video.mp4" />
-    </VideoSkin>
-    <SkipIntroButton />
-  </Container>
-</Player>
-```
-## Make it accessible
-- [Learn more about accessibility in video players](../concepts/accessibility.md)
-## Full example
-A “skip intro” button that appears during the first 30 seconds of playback and seeks past the intro when clicked.
-SkipIntroButton.tsx
-SkipIntroButton.css
-```
-// The preset's usePlayer is typed for its feature bundle
-import { usePlayer } from '@videojs/react/video';
-export function SkipIntroButton() {
-  const store = usePlayer();
-  const currentTime = usePlayer((s) => s.currentTime);
-  const paused = usePlayer((s) => s.paused);
-  const visible = currentTime < 30 && !paused;
-  return (
-    <button
-      className="skip-intro-button"
-      onClick={() => store.seek(30)}
-      aria-label="Skip intro"
-      // `undefined` removes the attribute; `false` would render data-visible="false"
-      data-visible={visible || undefined}
-      tabIndex={visible ? 0 : -1}
-    >
-      Skip intro
-    </button>
-  );
-}
-```
-```
-.skip-intro-button {
-  position: absolute;
-  bottom: 5rem;
-  right: 1rem;
-  opacity: 0;
-  pointer-events: none;
-  transition: opacity 200ms;
-}
-.skip-intro-button[data-visible] {
-  opacity: 1;
-  pointer-events: auto;
-}
-```
-Your component needs to be inside a player, such as [`<VideoPlayer>`](../reference/player.md), to access state. Place it inside [`<Container>`](../reference/player-container.md) if it should also participate in fullscreen and respond to user activity:
-tsx
-```
-import { Container } from '@videojs/react';
-import { Video, VideoPlayer, VideoSkin } from '@videojs/react/video';
-import '@videojs/react/video/skin.css';
-import { SkipIntroButton } from './SkipIntroButton';
-export default function App() {
-  return (
-    <VideoPlayer>
-      <Container>
-        <VideoSkin>
-          <Video src="video.mp4" />
-        </VideoSkin>
-        <SkipIntroButton />
-      </Container>
-    </VideoPlayer>
-  );
-}
-```
-## How it works
-Custom components read player state and dispatch actions through [features](../concepts/features.md). Each feature exposes a set. Here are some features you might reach for first:
-State
-Actions
-Feature
-`paused`, `ended`
-`play()`, `pause()`
-[Playback](../reference/feature-playback.md)
-`currentTime`, `duration`
-`seek()`
-[Time](../reference/feature-time.md)
-`volume`, `muted`
-`setVolume()`, `toggleMuted()`
-[Volume](../reference/feature-volume.md)
-`fullscreen`
-`requestFullscreen()`, `exitFullscreen()`
-[Fullscreen](../reference/feature-fullscreen.md)
-Browse the full list in the **Features** section of the sidebar.
-Access state and actions with the [`usePlayer`](../reference/use-player.md) hook from your player’s preset. It knows which features that preset has, so state and actions are typed. (The standalone `usePlayer` export from `@videojs/react` returns an untyped store, so its values are `unknown` in TypeScript.) If you built the player with a custom feature set through [`createPlayer`](../reference/create-player.md) — the escape hatch for custom feature sets — use the `usePlayer` it returns instead.
-tsx
-```
-import { usePlayer } from '@videojs/react/video';
-// Subscribe to state — re-renders only when selected values change
-const paused = usePlayer((s) => s.paused);
-const currentTime = usePlayer((s) => s.currentTime);
-// Get the store for dispatching actions (does not subscribe)
-const store = usePlayer();
-await store.play();
-store.setVolume(0.5);
-store.seek(30);
-```
-Custom controls also need real button semantics — the examples above set the accessible name, keyboard focus, and (in HTML, where there is no native `<button>`) the ARIA button pattern by hand.
-- [Learn more about accessibility in video players](../concepts/accessibility.md)
-## Availability and constraints
-*   Features are configured per player, so a feature your component asks for may not be present. Selectors return `undefined` for a missing feature; guard the value before using it, as the example does.
-*   Volume, fullscreen, picture-in-picture, and remote playback also expose an `*Availability` property (`'available'`, `'unavailable'`, or `'unsupported'`) for hiding controls the platform does not support. See [Features](../concepts/features.md) for details.
-## Common variations
-Before building from scratch, check if an existing approach covers your use case. Build a custom component when you need new behavior, a new state display, or integration with an external system.
-### Change what a built-in control renders
-Use the `render` prop on any built-in component. See [UI components](../concepts/ui-components.md).
-### Restyle a control
-Use CSS custom properties and data attributes. See [UI components](../concepts/ui-components.md).
-### Rearrange or remove controls
-Eject a skin and modify it. See [Customize skins](./customize-skins.md#eject-and-edit-a-skin).
-## Troubleshooting
-### State and actions are typed as `unknown`
-You’re using the standalone `usePlayer` export or the shared `playerContext`, which don’t know which features your player has. In React, import `usePlayer` from your player’s preset (for example `@videojs/react/video`), or use the hook returned by `createPlayer` if you built the player with a custom feature set. In HTML, use the typed `context` returned by `createPlayer`.
-### The component renders but never updates
-In React, the component sits outside the player (such as `<VideoPlayer>`), so `usePlayer` has no store to subscribe to. In HTML, the element sits outside `<video-player>`, or the class doesn’t extend `MediaElement`, so `PlayerController` has nothing to schedule updates on.
-## Related API
-*   [usePlayer](../reference/use-player.md)
-*   [PlayerController](/docs/framework/html/reference/player-controller)
-*   [createPlayer](../reference/create-player.md)
-*   [Player container](../reference/player-container.md)
-## Related guides
-*   [Customize skins](./customize-skins.md)

package/docs/how-to/cast-to-airplay-and-chromecast.md DELETED Viewed

@@ -1,158 +0,0 @@
-# Cast to AirPlay and Chromecast
-Send playback to AirPlay and Google Cast devices, with availability detection and connection state.
-Send playback to an Apple TV over AirPlay or a Chromecast over Google Cast while the browser stays in control.
-Note
-Using a pre-built [skin](../concepts/skins.md)? It already includes the controls shown here. You may still need the media or player setup in this guide. The component examples are for building your own player UI from individual [components](../concepts/ui-components.md).
-## Recommended approach
-Use the [GoogleCast extension](../reference/google-cast.md) with a [CastButton](../reference/cast-button.md), and add an [AirPlayButton](../reference/airplay-button.md) for Safari. The prebuilt skins already include both buttons; add `GoogleCast` next to a streaming media component to enable the configurable Cast route.
-App.tsx
-App.css
-```
-import { AirPlayButton, CastButton, Container, createPlayer } from '@videojs/react';
-import { GoogleCast } from '@videojs/react/extensions/google-cast';
-import { HlsJsVideo } from '@videojs/react/media/hlsjs-video';
-import { videoFeatures } from '@videojs/react/video';
-const { Player } = createPlayer({ features: videoFeatures });
-export default function BasicUsage() {
-  return (
-    <Player>
-      <Container className="media-container">
-        <HlsJsVideo src="https://stream.mux.com/BV3YZtogl89mg9VcNBhhnHm02Y34zI1nlMuMQfAbl3dM.m3u8" autoPlay muted playsInline loop />
-        <GoogleCast />
-        <div className="media-remote-buttons">
-          <AirPlayButton
-            className="media-airplay-button"
-            render={(props, state) => (
-              <button {...props}>{state.state === 'connected' ? 'Stop AirPlay' : 'Start AirPlay'}</button>
-            )}
-          />
-          <CastButton
-            className="media-cast-button"
-            render={(props, state) => (
-              <button {...props}>{state.connection === 'connected' ? 'Stop casting' : 'Start casting'}</button>
-            )}
-          />
-        </div>
-      </Container>
-    </Player>
-  );
-}
-```
-```
-.media-container {
-  position: relative;
-}
-.media-container video {
-  width: 100%;
-}
-.media-remote-buttons {
-  position: absolute;
-  right: 10px;
-  bottom: 10px;
-  display: flex;
-  gap: 8px;
-}
-.media-airplay-button,
-.media-cast-button {
-  padding-block: 8px;
-  padding-inline: 20px;
-  color: black;
-  cursor: pointer;
-  background: rgba(255, 255, 255, 0.7);
-  border: 1px solid rgba(255, 255, 255, 0.3);
-  border-radius: 9999px;
-  backdrop-filter: blur(10px);
-}
-.media-airplay-button[data-disabled],
-.media-cast-button[data-disabled] {
-  cursor: not-allowed;
-  opacity: 0.5;
-  filter: grayscale(1);
-}
-```
-The demo pairs the streaming media component with the `GoogleCast` extension in React or `<google-cast>` in HTML. Without that extension, `CastButton` drives the browser’s native Remote Playback API instead, which does not provide Video.js receiver or load-request configuration.
-## How it works
-The [remote playback feature](../reference/feature-remote-playback.md) gives AirPlay and Google Cast one state shape:
-*   `remotePlaybackAvailability` is `'available'` when a remote device can be reached, `'unavailable'` when the API exists but no device is reachable, and `'unsupported'` when the browser has no remote playback route.
-*   `remotePlaybackState` is `'disconnected'`, `'connecting'`, or `'connected'`.
-*   `toggleRemotePlayback()` opens the browser’s device picker, or disconnects an active session.
-AirPlay uses WebKit’s presentation APIs. Google Cast uses a sender and receiver: the browser sends the receiver a media URL and then controls playback. Your UI reads the same Video.js state for either route.
-While connected, playback actions — play, pause, seek, volume — proxy to the remote device, and player state keeps reflecting the remote session. Local playback is suspended.
-The Google Cast SDK loads only when the `GoogleCast` extension is present in a Chromium browser. Players without that extension and browsers that cannot cast do not load it.
-## Availability and constraints
-*   Remote playback is asynchronous and can fail mid-session when a device or network disappears. React to `remotePlaybackState` rather than assuming a request succeeds.
-*   Google Cast works only in Chromium-based browsers; elsewhere its route reports `'unsupported'`.
-*   AirPlay works only in Safari; availability requires an AirPlay device reachable on the network.
-*   The remote device fetches the source and tracks itself. Localhost, VPN-only, expired, or cross-origin URLs without the necessary CORS headers will fail on the receiver even if they play in the browser.
-*   Set `disableRemotePlayback` on the media element to opt out entirely.
-## Common variations
-### Custom Cast receiver
-By default, Video.js sends the current source to Google’s Default Media Receiver. Set `receiver` when you have your own receiver application:
-tsx
-```
-<GoogleCast receiver="YOUR_APP_ID" />
-```
-Use `src` and `contentType` when the receiver should load a different source than the browser. `streamType` and `customData` let you describe that source and attach application-specific data. See the [GoogleCast reference](../reference/google-cast.md) for the exact option types and HTML property mapping.
-### Read connection state
-Use `remotePlaybackAvailability` to decide whether to offer a route and `remotePlaybackState` to show whether it is disconnected, connecting, or connected. `CastButton` and `AirPlayButton` already apply these states to their presentation; read them directly only when another part of your app needs them.
-## Troubleshooting
-### The cast button doesn’t render, or renders disabled
-The Cast button hides when the route is unsupported. In Chromium with no Cast device reachable, it stays visible but disabled. The AirPlay button hides unless Safari reports an AirPlay device.
-### Casting starts but the device shows an error
-The receiver cannot fetch the media. Confirm the source URL is reachable from the device and served with CORS headers, including caption tracks.
-### The UI freezes on “connecting”
-The user dismissed the picker or the device disconnected. `remotePlaybackState` returns to `'disconnected'`; drive your UI from that state.
-## Related components
-*   [Cast button](../reference/cast-button.md)
-*   [AirPlay button](../reference/airplay-button.md)
-*   [GoogleCast](../reference/google-cast.md)
-## Related API
-*   [Remote playback feature](../reference/feature-remote-playback.md)
-*   [HlsJsVideo](../reference/hlsjs-video.md)
-## Related guides
-*   [Media sources](../concepts/media-sources.md)