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

powertrain

v2.0.0

Published

A lightweight game loop written to prioritize updates and fill in with extra renders.

Downloads

21

Readme

Powertrain

A lightweight game loop written to prioritize updates and fill in with extra renders.

Updates will be called as accurately as possible while render operations will happen as often as possible. If, for some reason, lag has caused more than enough time for more than one update to occur they will be called sequentially until caught up. A render will always happen afterwards upates are done.

Testing and dev are done with babel.

import Powertrain from 'powertrain'

const engine = new Powertrain({
  playspeed: 1,     // optional, default = 1
  fps: 60,          // optional, default = 60
  update: () => {}, // optional, default = no-op
  render: () => {}, // optional, default = no-op
})

engine.start()
engine.stop()

Usage

NPM

constructor()

|Name | Type | Attributes | Default | Description | |---------------|----------|------------|--------------|---------------------------------| | obj.playSpeed | number | | 1 | A scalar for the speed of play. | | obj.fps | number | | 60 | The target fraes per second. This is the number of updates per second that should occur. Not the number of renders. | | obj.update | function | | ()=>{} | The function to update game logic. | | obj.render | function | | (scalar)=>{} | The function to render the game. Accepts a scalar representing progress towards next frame. Can be used for interpolation. |

start()

Starts update loop and sets running flag to true and calls for a requestAnimationFrame (provided by a crossplatform polyfill).

stop()

Sets running flag to false. This will stop the loop.

TODO:

Feedback ✉️

It is greatly appreciated! 🎉

Website 🌐

[email protected]

https://github.com/limeandcoconut

@limeandcoconut 🐦

Cheers!

License

ISC, see LICENSE.md for details.