dan

> reading https://github.com/reactjs/react-future/blob/master/01%20-%20Core/02%20-%20Mixins.js it seems clear where react is heading I would not say so: https://twitter.com/sebmarkbage/status/571389309586051072 > I'll focus on making composition easier so we can get rid of mixins....

Yes, I'm in favor of any userland solutions like this one.

With Redux, I'd implement a generic store (or a higher-order store) for pagination and use [store functional composition](https://gist.github.com/gaearon/d77ca812015c0356654f) to reuse this functionality across different stores.

FWIW Redux today has an [example with pagination](https://github.com/rackt/redux/tree/master/examples/real-world). It is implemented as a [reducer factory](https://github.com/rackt/redux/blob/master/examples/real-world/reducers/paginate.js).

Flummox, from what I know, doesn't override `console` methods or anything. Any chance your build tool (responsible for source maps) is configured incorrectly or is at a buggy version?

Can you try changing `devtool` in your Webpack config to `'eval'`? This sure looks like a broken source map.

Note that after some discussion, we might not include the plugin after all. I'm worried it will too often be unactionable especially for tiny deps where this doesn't matter (e.g....

That would make sense, but it's not obvious how the plugin could measure that.

Yeah it's pretty frustrating. And also understandable because many people don't know what things like "regex ddos" means or even how webapps work in general. So I understand that it...

>However, if we have seen/ are seeing there are hundreds of issues with thousands of comments on those 96 vulnerabilities (as you said 'false positives'), this should have been fixed...