Hello. I've been updating ionic but, as it uses native-run to run on my android device, i don't have seen it update it. Like, i run npm i -g ionic and it updates ionic, but i have to update native-run manually. It is a very hard thing to remember, as i only have the time to update it if i stick a note somewhere or if i'm updating everything on my project. It's a bad behavior to have this tools separated, as it excludes the idea of transparency. If you change the tool to run on devices as a separated tool/dependency, like you first did with the 5.0.0 update (i had to run with the flag --no-native-run for a time before the bugs were fixed), then i think is best if you actually manage this dependency and update it to a better user experience. Same thing with cordova-res.
Hello. I've been updating ionic but, as it uses native-run to run on my android device, i don't have seen it update it. Like, i run
npm i -g ionicand it updates ionic, but i have to update native-run manually. It is a very hard thing to remember, as i only have the time to update it if i stick a note somewhere or if i'm updating everything on my project. It's a bad behavior to have this tools separated, as it excludes the idea of transparency. If you change the tool to run on devices as a separated tool/dependency, like you first did with the 5.0.0 update (i had to run with the flag --no-native-run for a time before the bugs were fixed), then i think is best if you actually manage this dependency and update it to a better user experience. Same thing with cordova-res.