Brandon Dail

We should also look into utilizing benchmark.js here as well. It does a lot of work making sure that it has enough runs to provide a statistically relevant result.

@ryan-roemer how does it compare with newer versions of Node?

@ryan-roemer thanks! I added it to the benchmark [repo](https://github.com/aweary/string-concat-array-join-bench) and updated the results in the README for all versions. Side note: it's amazing how much faster string concatenation has gotten...

@alextait1 as far as I can tell it should be reproducible in any environment that is rendering a `Pressable` with an `onLongPress` listener. I am using a [Logitech K380 Multi-Device...

To clarify, are you looking to add a better error message for all instances where `prop-types` receives `undefined` or some other unexpected type for the input value? If this would...

@mondwan can you share an example reproducing the issue? I'm not seeing the warning when using the latest `create-react-class` version, or the last 15.5 release. [Example](https://jsfiddle.net/sch60ss0/). You can use [this...

@mondwan the issue is that you're using the minified `create-react-class` build, but the unminified `react` build. This means that the internal flag that `create-react-class` uses to suppress this warning is...

Because `getDefaultProps` is only used for components created with `createReactClass`. For example, the warning will catch cases where someone is moving from `createClass` to ES6 classes and they forget to...

You're getting the warning because you're using the production `create-react-class` build with the development `react` build. The production build strips out the code that prevents this warning in development

@nhunzaker feel free to look into this 👍 I did some very shallow/quick debugging and from what I can tell iOS Safari is not updating the DOM element's `.value` property...