Jesse Skinner

If anyone came here looking for a workaround for the ability to call `res.once('drain', ...)` without have node warn about `MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added...

Would implementing `` here address the issue? See https://prettier.io/docs/en/ignore.html Seems it is already partially implemented for HTML, but not for `` and ``.

That looks interesting as an alternative to passing around a store as a prop, and way better than using global variables for stores. My understanding is that contexts remain an...

I'm going to give this another shot and come up with a React component that can be used to provide props and actions to a subset of the React render...

I tinkered around with context, but I think I found a nicer approach that doesn't use context. I found that being forced to use this.context contentTypes etc. was a bit...

I may have found a bug in React that discouraged me from using context. It seems props.children aren't re-rendered when the context (or state) changes. You have to do a...

Ah - this is known, and is in discussion. So I think a good context-based solution will need this to be figured out first. https://github.com/facebook/react/issues/2517

@prabirshrestha In my example, you create a new store using `nameActions` every time you create a ``, and the contents get updated whenever that store instance's state changes. So I...

And I guess if you already had stores and wanted to reuse them, you could modify the `` and change this line: ``` javascript var actions = Hoverboard(this.props.actions); ``` to...

Thanks Mike. I'm not familiar with TypeScript, but if you know what changes would be necessary in Hoverboard, I'd encourage you to fork the repo, add these typings, and submit...