Chion
Yeah I confirmed this issue. There are some width calculation problems in the Tab update hooks. Will fix later.
@RangerMauve Worth trying. The tab bars are originally migrated from `react-native-scrollable-tab-view`, where widths are computed by javascript on the fly. I modified some of those code to make it work...
Consider separating `native-base-web` and `react-native-web` into a webpack DLL module. Or try using webpack2 where you can enable the tree-shaking feature to shrink the bundle.
@coryarmbrecht v2.0 is not supported by the moment and we still have much to do. Please lock `react` to `15.4.1` and `react-native-web` to `0.0.60`.
@srt0422 v0.5.4
Agree. I've done the major migration to make `native-base-web` run on `react-native-web`. Read [Manual Setup](https://github.com/Chion82/native-base-web/blob/dev/README.md#manual-setup) for details. As for `react-native-web-extended`, it has been merged with the latest upstream branch currently....
Downgrading React to `15.4.1` should solve the problem. If you are using features from the latest React, keep using this workaround. NativeBase V2 support is currently suspended because we have...
Great idea! I really love to. We need people to collaborate on this project and make further progress. Anyway thanks for your support! That means a lot :)
这种情况是否出现在同五元组的流量一直持续，而中途路由出口变更的情况下？ 本模块内的映射表存活状态理应不会影响到内核的 CT 表，可能是使用了模块内过期的映射表项导致的。 如果路由出口变更后，客户端停止流量，过几分钟后再使用同样的五元组发包，能否成功重新建立 NAT 会话？
@liangchen2233 抱歉，之前测试环境坏了一直没有验证这个 pull request。能否测试一下 #19 是否解决了这个问题？