Moment-timezone: Update main in bower.json with new filename

[jishaal]

Latest 0.15.12 releases updated and renamed moment-timezone-with-data-2010-2020.js to moment-timezone-with-data-2012-2022.js, however the main field entry point when using bower needs to be updated as well.

[QuentinFchx]

Also, could we avoid patch releases for _breaking_ changes like this one?

[Multiply]

Same issue for us. It shouldn't have been done in a patch release :(

Edit:
We ended up using the overrides option in our own bower.json, and set the main file, to link to ./builds/moment-timezone-with-data-2012-2022.js, and it started working again.

[igor-shevchenko]

If you want to temporarily work around the problem, you can add an override to your bower.json:

{
  "name": ...,
  "dependencies": ...,
  ...
  "overrides": {
    "moment-timezone": {
        "main": "builds/moment-timezone-with-data-2012-2022.js"
    }
  }
}

[mj1856]

Fixed the bower.json file. My mistake. Apologies.

WRT breaking changes - please keep in mind that moment-timezone is still 0.x. Per SemVer #4, anything may change at any time.

Still, sorry for the confusion. In retrospect, I believe we will change this before 1.0 to not have years in the file name, thus avoiding breaking changes from one year to the next.

[mj1856]

Also, if you're still having problems because Bower cached the previous copy, do:

bower cache clean moment-timezone

Then reinstall and it should work.

[tkarls]

Thanks. Works now!