Ionic 2.0 Final

So uninstall, etc, etc. and reinstalled ionic2. Created a new v2 app to compare. Then used NCU to see if there were any outdated dependencies.

Using …\ionic\cutePuppyPics\package.json
[…] \ :
@angular/common 2.2.1 → 2.4.9
@angular/compiler 2.2.1 → 2.4.9
@angular/compiler-cli 2.2.1 → 2.4.9
@angular/core 2.2.1 → 2.4.9
@angular/forms 2.2.1 → 2.4.9
@angular/http 2.2.1 → 2.4.9
@angular/platform-browser 2.2.1 → 2.4.9
@angular/platform-browser-dynamic 2.2.1 → 2.4.9
@angular/platform-server 2.2.1 → 2.4.9
@ionic/storage 1.1.7 → 1.1.9
ionic-native 2.4.1 → 2.7.0
rxjs 5.0.0-beta.12 → 5.2.0
sw-toolbox 3.4.0 → 3.6.0
zone.js 0.6.26 → 0.7.7
@ionic/app-scripts 1.1.3 → 1.1.4
typescript 2.0.9 → 2.2.1

Really? Not even shipping with the latest version of your own @ionic/storage or ionic-native? And that out of date on rxs and typescript?

Are there any timeframes on getting the dependencies updated? Yes I saw that you are working on loadtimes, etc. but nonetheless.

Have you considered that there are ore than 1 person concurrently working on all these things? So while A is finishing up the Ionic 2 final release, maybe B is working on the next version of something else. Should A add another two weeks to get the new version from B integrated?

That may fly for the two iconic dependencies. However considering how far behind the external dependencies are that doesn’t fly in those cases. It’d be one thing if they were off by a patch or two. But in some cases its a beta to a non-beta build (rxjs).

In software development, as you work on new features and capabilities, you need to keep your dependencies up-to-date. Especially when you are going to deliver a ‘final’ (which is a bad name anyways). You should have had a code freeze at given sprint for new features, and had a sprint or two to make sure your dependencies are updated and not presenting any show stopping issues.

This (dependencies being out of date) is generally not an oversight; it’s a result of known upstream changes that are incompatible with framework code. That’s just a fact of life when dealing with such a huge codebase. You’re always free to try building against newer versions of dependencies; just make sure you verify that any issues you encounter aren’t a result of going off reservation like that before reporting them as bugs and do your best to monitor issue trackers for the location of known potholes.