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

framerate-history

v1.0.18

Published

An ES6 class for tracking framerate for a given period of time.

Downloads

155

Readme

Framerate History

An ES6 class for tracking framerate for a given period of time.

npm deps size vulnerabilities license

Installation

npm install framerate-history

FrameRate

import FrameRate from 'framerate-history';

new FrameRate(settings)

| Param | Type | Default | | --- | --- | --- | | settings | Object | | | [settings.onSample] | function | | | [settings.filterStrength] | Number | 5 | | [settings.historyDuration] | Number | 30 | | [settings.sampleRate] | Number | 10 |

frameRate.fps ⇒ Number     🔒 Read only

The last recorded FPS

frameRate.history ⇒ Array     🔒 Read only

The FPS recordings over the history duration

frameRate.filterStrength([value]) ⇒ Number     🔗 Chainable

Sets a filter on the frame rate calculation. Setting to 1 will effectively turn off the filter, the higher the number the more smooth the curve over time. See this stackoverflow question for details: https://stackoverflow.com/questions/4787431/check-fps-in-js

Default: 5

| Param | Type | | --- | --- | | [value] | Number |

frameRate.sampleRate([value]) ⇒ Number     🔗 Chainable

The rate to take samples. Setting to 0 will clear the interval. If the interval is prevented from executing at the desired rate, the history will get filled in with the current frame rate in an attempt to keep the history as accurate as possible.

Default: 10

| Param | Type | Description | | --- | --- | --- | | [value] | Number | Samples per second |

frameRate.onSample([callback]) ⇒ function     🔗 Chainable

The callback will get called for every sample taken.

| Param | Type | Description | | --- | --- | --- | | [callback] | function | The callback is given one param, the FPS history array. |

frameRate.historyDuration([value]) ⇒ Number     🔗 Chainable

Defines the duration of tracked history.

Default: 30

| Param | Type | Description | | --- | --- | --- | | [value] | Number | Seconds |