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

tachyon-pulsar

v32.0.0

Published

Pulsar Re-Export Of Submodules

Downloads

3

Readme

Pulsar

Re-export of Pulsar packages conveniently under a single import namespace for consumers.

How It Works

  1. Create a src URL using the provided manifest URL utils.
  2. Select a Pulsar backend (PulsarCore, PulsarNative, etc) and render the provided component with the desired initial playback state.
  3. Use the Player-Controller Context API to interact with player state and build custom UI.
  4. Use one of the provided analytics hooks to receive fully formed player tracking events.

Note: Pulsar Backends can be used interchangeably with the Player-Controller API and analytics hooks.

Example

import { createStreamManifestUrl, PlayerControllerRoot, PulsarNative, usePlayerController, useStreamAnalytics } from 'pulsar';

export const BasePlayer = () => {
  const controller = usePlayerController();

  // To get player tracking events, use one of the provided content type hooks
  useStreamAnalytics({ onTrackingEvent: () => { /*...*/}, ... });

  // Create a manifest URL
  const streamSourceUrl = createStreamManifestUrl({ ... });

  return (
    <PulsarNative autoPlay muted controls src={streamSourceUrl} />
  );
}

export const Player = () => (
  <PlayerControllerRoot>
    <BasePlayer />
  </PlayerControllerRoot>
);

Video Formats, Codecs and Containers

For a brief primer on all of these topics, watch this video.