The doc for componentOnReady recommends Ionic's similarly-named util for consistent behavior between lazy and non-lazy-loaded builds:
If you want to simulate the behavior of componentOnReady() for non-lazy builds, you can implement a helper method to wrap the functionality similar to what the Ionic Framework does here.
A note should be added this being similar in functionality in the non-lazy-loaded builds only if none of the component lifecycle methods return a promise. Otherwise, the callback will resolve after a requestAnimationFrame, but possibly before async component lifecycle methods resolve.
The doc for
componentOnReadyrecommends Ionic's similarly-named util for consistent behavior between lazy and non-lazy-loaded builds:A note should be added this being similar in functionality in the non-lazy-loaded builds only if none of the component lifecycle methods return a promise. Otherwise, the callback will resolve after a
requestAnimationFrame, but possibly before async component lifecycle methods resolve.