Peace

@excitement-engineer this is still a problem

PR #31 fixes this. My previous commits have not been merged and the latest commit stacks onto those.

Still waiting on @ananddayalan to merge my PR. In the meantime, you can use my fork by directly pointing the dependency to the repo: ``` "dependencies": { "react-native-material-design-searchbar": "git+https://github.com/peacechen/react-native-material-design-searchbar.git", ......

Looks like this was fixed in https://github.com/ananddayalan/react-native-material-design-searchbar/commit/d9987c18c6a0663a5bcdfbd4b87d204f2f45e1e3 Is that working as you expect?

The community side menu and drawer components are designed to act as routers which rules them out for my project. They also have trouble integrating with NavigationExperimental. I'm looking for...

Thanks for posting the demo. rn-dom's built-in native modules are also a good reference. Since I'm not using ES7 decorators, it's been a challenge finding the right equivalent ES6 syntax....

After futzing around with desugaring ES7 decorators to ES6, I found this to work: ``` class myClass { constantsToExport() { return { "someConstant": "someValue", // ... } } } RCT_EXPORT_MODULE("myClass")(myClass);...

Thanks @vincentriemer This now works: ``` export default RCT_EXPORT_MODULE("myNativeClassName")(myClass) ```

This could be addressed by transpiling to ES5 using Webpack or Browserify. Projects consuming this may need to turn on the switch to transpile source under node_modules. That could slow...

Here's a walk-through for Webpack. There are tutorials out there for Bable and Browserify too. https://medium.com/unhandled-exception/using-non-transpiled-modules-and-webpack-657dca27bd4a