Kevin C

@kketch with that example repo, simply start the server and hit it with any invalid request that causes some sort of error to be thrown and you'll see the warnings...

Hmm, in my opinion it makes sense as-is, no changes to the libraries needed -- I updated my server code to match your example above and it works great! If...

This is a few years old now and the suggested workaround did not work for me: the empty option was ignored and not rendered. I ended up using `allowClear: true`...

@brunolemos I think this is a dupe: https://github.com/vacuumlabs/babel-plugin-extensible-destructuring/issues/14. Can you try again on latest version of RN?

Thanks for the info @lucasleelz. I think this may be fixed by an upcoming PR. Feel free to check out the code and try it yourself: https://github.com/vacuumlabs/babel-plugin-extensible-destructuring/pull/20

I started getting this error again as of RN v0.43; I made a PR to improve debug messages: https://github.com/facebook/react-native/pull/13561. You can manually copy the changes there into your `node_modules/react-native` (at...

According to [Mac support](https://support.apple.com/en-us/HT202491) you can add an exception under Security & Privacy. Just click the lock icon, enter your password, and click Allow Anyway:

Duplicate of https://github.com/sketch-hq/print-export-sketchplugin/issues/32

Hi @ashaindlin, not sure if you're monitoring this repo but I'd love to hear your thoughts on this.

It would be great to have a `--dry-run` flag for publishing. With npm you can use `npm pack` to generate a tar that's exactly the same as the release contents,...