Under the hood hot module replacement (hmr) performs a special kind of navigation action to apply the changes on the fly. Currently we would use the default navigation transition (or the last applied navigation transition) for this "replace" navigation as the idea is to provide some visual indicator that hot module replacement occurred. However, this behavior is not consistent across iOS and Android at the moment (e.g. each platform has different default transition), and if the last applied transition was Flip, it is quite weird to constantly "flip" the view on each hot module replacement update. Moreover, the fact that we do a special "replace" navigation internally for hot module replacement should be transparent to the app developer.
As an enhancement we decided to provide a consistent quick(100ms) fade transition on both iOS and Android when performing the "replace" navigation.
Under the hood hot module replacement (hmr) performs a special kind of navigation action to apply the changes on the fly. Currently we would use the default navigation transition (or the last applied navigation transition) for this "replace" navigation as the idea is to provide some visual indicator that hot module replacement occurred. However, this behavior is not consistent across iOS and Android at the moment (e.g. each platform has different default transition), and if the last applied transition was Flip, it is quite weird to constantly "flip" the view on each hot module replacement update. Moreover, the fact that we do a special "replace" navigation internally for hot module replacement should be transparent to the app developer.
As an enhancement we decided to provide a consistent quick(100ms) fade transition on both iOS and Android when performing the "replace" navigation.