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

rvfc-polyfill

v1.0.7

Published

requestVideoFrameCallback polyfill

Downloads

14,608

Readme

requestVideoFrameCallback polyfill

Usage:

npm install rvfc-polyfill
import 'rvfc-polyfill'

Warning: this polyfill is at BEST roughly accurate as it runs using RAF, which is bound to the window's framerate, unlike RVFC which is bound to the video's framerate [but still capped by the window's framerate].

Because this polyfill uses RAF, the timestamps reported are ones used by the DOM renderer, rather than video decoder. Notable differences:

  • presentationTime - time when a new painted frame was detected, this is the time of when a RAF was fulfilled + the time it took to paint the last frame [rough estimate]
  • expectedDisplayTime - time when the RAF was fulfilled + the time it takes to render a frame on the browser
  • mediaTime - time of the video when the RAF was fulfilled - processingTime [this ISNT the video time when a video frame was decoded, but is closely accurate]
  • presentedFrames - if the video framerate is higher than the browser window framerate, this will omit frames
  • processingDuration - time it took to paint a frame

Notable examples: Given a video with 50 fps and having the browser window limited to 60 fps the mediaTime reported will be in order:

By the original:

  • 0.001
  • 0.021
  • 0.043
  • 0.064
  • 0.084
  • 0.106

By this polyfill:

  • 0.001
  • 0.027
  • 0.041
  • 0.066
  • 0.081
  • 0.108

[+- 5ms as the highrestimestamps reported by browsers are marginally inaccurate] which means the times arent inline with the video frames