npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@atom-platform/ngx-plyr

v17.3.2

Published

Angular 17+ bindings for [plyr video and audio player](https://github.com/sampotts/plyr). Supports everything that original library supports.

Downloads

490

Readme

Atom-Platform ngx-plyr for Angular

Forked from smnbbrv/ngx-plyr, but this version supports angular 17+

@atom-platform/ngx-plyr

Angular 17+ bindings for plyr video and audio player. Supports everything that original library supports.

Push

Installation

npm i plyr @atom-platform/ngx-plyr

TypeScript typings

As long as original plyr does not have yet (sigh) typings, this project has its own at typings/plyr/index.d.ts.

If you have typings issues please refer to the issue #7 for more info.

Usage

Import PlyrModule into the current module's imports:

import { PlyrModule } from '@atom-platform/ngx-plyr';

imports: [
  // ...
  PlyrModule,
],

Finally use plyr in your components as attribute:

<div
  plyr
  style="width: 640px;"
  plyrTitle="Video 1"
  [plyrPlaysInline]="true"
  [plyrSources]="videoSources"
  (plyrInit)="player = $event"
  (plyrPlay)="played($event)"
></div>

<button (click)="play()">Play</button>

or tag (remember that in this case plyr tag has display: inline which cannot accept width, so you need to care of this):

<plyr
  style="display: block; width: 640px;"
  plyrTitle="Video 1"
  [plyrPlaysInline]="true"
  [plyrSources]="videoSources"
  (plyrInit)="player = $event"
  (plyrPlay)="played($event)"
></plyr>

<button (click)="play()">Play</button>

and the component file would have

// get the component instance to have access to plyr instance
@ViewChild(PlyrComponent)
plyr: PlyrComponent;

// or get it from plyrInit event
player: Plyr;

videoSources: Plyr.Source[] = [
  {
    src: 'bTqVqk7FSmY',
    provider: 'youtube',
  },
];

played(event: Plyr.PlyrEvent) {
  console.log('played', event);
}

play(): void {
  this.player.play(); // or this.plyr.player.play()
}

For using with hls.js and dash.js check the examples and implementation of this project's src/app folder.

API

The API mostly replicates the original Plyr API. See https://github.com/sampotts/plyr for more info

Inputs

Important: changing plyrOptions, plyrPlaysInline and plyrCrossOrigin will trigger the Plyr reinitialization, since these options cannot be changed on-the-fly

Events

ngx-plyr events:

  • plyrInit: emits a plyr instance when it gets created

plyr events:

  • plyrProgress: replicates original progress event

  • plyrPlaying: replicates original playing event

  • plyrPlay: replicates original play event

  • plyrPause: replicates original pause event

  • plyrTimeUpdate: replicates original timeupdate event

  • plyrVolumeChange: replicates original volumechange event

  • plyrSeeking: replicates original seeking event

  • plyrSeeked: replicates original seeked event

  • plyrRateChange: replicates original ratechange event

  • plyrEnded: replicates original ended event

  • plyrEnterFullScreen: replicates original enterfullscreen event

  • plyrExitFullScreen: replicates original exitfullscreen event

  • plyrCaptionsEnabled: replicates original captionsenabled event

  • plyrCaptionsDisabled: replicates original captionsdisabled event

  • plyrLanguageChange: replicates original languagechange event

  • plyrControlsHidden: replicates original controlshidden event

  • plyrControlsShown: replicates original controlsshown event

  • plyrReady: replicates original ready event

  • plyrLoadStart: replicates original loadstart event

  • plyrLoadedData: replicates original loadeddata event

  • plyrLoadedMetadata: replicates original loadedmetadata event

  • plyrQualityChange: replicates original qualitychange event

  • plyrCanPlay: replicates original canplay event

  • plyrCanPlayThrough: replicates original canplaythrough event

  • plyrStalled: replicates original stalled event

  • plyrWaiting: replicates original waiting event

  • plyrEmptied: replicates original emptied event

  • plyrCueChange: replicates original cuechange event

  • plyrError: replicates original error event

  • plyrStateChange: replicates original statechange event

Getters and setters / Methods

You can use standard getters and setters and methods by getting Plyr instance from plyrInit.

Custom Plyr driver

The library allows you to go in its heart by defining a custom Plyr driver. What it means: the hardest stuff is still done for you, but you can apply some actions in the critical points like creating the Plyr instance, updating and destroying it.

This is the right place for integration with other libraries like hls.js, dash.js etc.

The default implementation looks like this:

import Plyr from "plyr";
import {
  PlyrDriver,
  PlyrDriverCreateParams,
  PlyrDriverUpdateSourceParams,
  PlyrDriverDestroyParams,
} from "./plyr-driver";

export class DefaultPlyrDriver implements PlyrDriver {
  create(params: PlyrDriverCreateParams) {
    return new Plyr(params.videoElement, params.options);
  }

  updateSource(params: PlyrDriverUpdateSourceParams) {
    params.plyr.source = params.source;
  }

  destroy(params: PlyrDriverDestroyParams) {
    params.plyr.destroy();
  }
}

You can create your own driver and pass it as input parameter to the plyr component.

Integrations

To integrate the library with hls.js and dash.js see the corresponding demo source code. To integrate others, use same approach with a custom Plyr driver.

License

MIT