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

react-phaser-kit

v0.1.1

Published

React component kit for Phaser game engine

Downloads

10

Readme

React Phaser Kit

a (raw, unfinished) custom React Fiber renderer for Phaser 3

Open questions:

  • Is React performant enough for this to even make sense?
    • Initial experiments with 60FPS show setState/re-rendering can take under 1ms, so... maybe?
    • Complex games might be a no-go without optimization
  • I've been waffling between the custom Fiber renderer approach. and simply doing everything in ReactDOM components.
    • ReactDOM components is much less complex to implement, easier to read, and mostly does the same stuff (checking props and applying them to phaser objects ('rendering'), sometimes calling phaser functions)
    • Potential performance optimizations from a custom fiber renderer?
      • No ReactDOM dependency (unless you want a React UI overlay in DOM which seems like a main reason you'd want to do this anyway)
      • Update: custom renderer is much more performant. why???

check out the demo!!!

Image of example code in browser

i need better example code but here's part of example/PhaserExampleComponent.js for now:

<React.Fragment>
  <updater
    onUpdate={this.handleUpdate}
    watchKeys={[KeyCodes.W, KeyCodes.A, KeyCodes.S, KeyCodes.D]}
  />
  <text
    x={25}
    y={25}
    style={{
      fontFamily: 'Helvetica',
      fontSize: 24,
      fill: '#ffffff',
    }}
  >
    {`Hello world ${Math.round(this.state.time, 1000)}`}
  </text>
  <sprite
    x={this.state.x + (30 * Math.sin(this.state.time / 195))}
    y={this.state.y + (30 * Math.cos(this.state.time / 195))}
    image={mushroom}
    tint={color}
    onClick={this.setRandomColor}
  />
  <graphics lineStyle={{ width: 10, color }} x={this.state.x} y={this.state.y}>
    <circle radius={120 + (20 * Math.sin(this.state.time / 195))} />
  </graphics>
</React.Fragment>

see example/example.js for a showcase / usage experimentation.

extremely in flux, will break.

my original approach used a custom React Fiber renderer/reconciler (it was much harder than this!) but i didn't see any clear benefit over this ReactDOM component-only approach. maybe a benefit (perf?) will become clear as i try more complex games with this setup and i'll try switching back.