react-canvas-stats

react-canvas-stats
========

#### React version of stats.js ####

Please see the original for a better idea of what this does. There's another react version of this but it hasn't been updated in a long time and renders this with the dom.

$3


Only the MS and FPS panels are available.

Pass a timestamp prop to the component when update needs to occur.


``javascript


import Stats from 'react-canvas-stats'


class Foo extends Component {

state={ timestamp: null }

//an example how to add the memory panel
constructor() {
super()

const memory = window.performance && window.performance.memory

if (memory) {
this._extraPanels = [
{
name: 'MB',
fg: '#f08',
bg: '#201',
maxValue: memory.jsHeapSizeLimit / 1048576, //you have to provide this for scale
updateOnType: 'fps', //this feels a bit clunky, there are two update types
updateCallback: val => memory.usedJSHeapSize / 1048576 //a function to transform the value (you dont have to you can also just compute whatever you want), val input val output
}
]
}
}

onSomeUpdate = ()=>{
this.setState({timestamp: Date.now()})
}

render(){

timestamp={this.state.timestamp} extraPanels={this._extraPanels}
/>

}
}

`

$3

Stats.js has been refactored. The idea is to have it not coupled with the dom, nor the panel instances for that matter. It's responsibilities should be:
- Figure out which now() is available.
- Compute miliseconds
- Compute frame rate.
- (memory has been nuked)

The react` side of things is relying heavily on timestamps. It feels kinda weird but it works. This seems to be an obvious way to trigger a change. For the main component, only the stamp of the last update is needed. The panel's seemed to each need their own, since the numbers could be the same (60fps over and over again) and it seemed like this change wouldn't register and the graph wouldn't progress. Hence both the value prop, and the time of last update.

$3

- research how to publish this. I don't understand how it should be bundled for npm.