gadicc
2.x update hassles
TL;DR; If you were successfully running v2.14.0 (only!) and got errors after upgrading to v2.14.2, you can (probably) just upgrade to the latest / v3 release to get everything working again.
No other versions were affected. Notably, upgrading from the popular v2.13.3 release did not have this isssue. My apologies for anyone who was affected by this.
Longer story:
9 months ago, I accidentally published some v3 code to the 2.x branch, and it was released as version v2.14.0. Upon realising my mistake, I fixed all the relevant version tags, but didn't actually unpublish the release.
That would have been fine for anyone updating to latest, but not for anyone using something like npm update with a version range like ^2.x.x. They would have gotten upgraded to 2.14.0 and suffered from some immediate errors because upgrading from v2 to v3 requires some code changes as described in UPGRADING.md.
Amazingly, no issues were opened about this in 9 months (and indeed, looking at the download stats, many more people were "correctly" downloading v2.13.3). However, I recently pushed a "final" v2.14.2 which is the same code as old v2.13.3 but with a warning that v2 is no longer supported.
Apologies if your project previously broke unexpectedly on the 2.14.0 upgrade, and if it now broke again on the 2.14.2 upgrade. However, if you previously updated your code to work on 2.14.0, likely just upgrade to v3 release with no other changes, to get back up and running. I still however apologise for the inconvenience.
I'm around if anyone is having any issues with this. But the advice remains the same, simply upgrade to v3 and make sure you follow the steps in the UPGRADING.md file if you haven't already.
