Is there anyway we could get some insight into how dependencies in Cordova packages can become an issue with upgrading across Meteor versions.
I’ve just upgraded to 1.6 and i’m filled with regret. I definitely still have a lot to learn, and I know i’m probably not managing everything correctly, but i feel that everyone tries to encourage fast adoption of the latest major Meteor versions, but if you are not comfortable with dependency management or manipulating build directories etc… that you should be very very very cautious about upgrading Meteor.
Especially if you have a stable app ready for production. Unless anyone can tell me why i’m wrong? I sincerely hope i’m wrong or missing something important. Which is almost definitely the case.
After a day of scanning the internets I find that… it’s easy to see that this has been an ongoing issue for many developers. Often posts on Cordova issues have zero replies or dozens of thumbs up and no solutions proffered or vaguely documented circumstantial fixes/hacks/patches…
basically there seems to be a lack of a coherent strategy from anyone official.
I’m not saying it has to work out of the box… Cordova is its own beast. But if Meteor aims to truly support cross-platform development, as it claims, then this is an issue which deserves more focus, and at the very least an entry in the Guide on how to deal with issues which may arise when upgrading
Stack Overload is filled with threads closed due to the lack of reproducible issues. That’s convenient for developers looking to close off bug threads, but it’s no help to those of us who have chosen to use Meteor for anything but a website.
this is a fun chain of links
These are just a quick sample of people with issues in this area.
anyway, rant over.