[rhinoceraptor]

Did babel force you to upgrade right when version 6 came out? They bumped the major version, that should be a pretty clear indicator that existing workflows will break.

Whenever you use a tool, you're accepting risk for the reward you're getting from it. If I run Gentoo on my servers, it's not really fair to complain when an update breaks something.

[atemerev]

JavaScript world is known by moving fast and breaking things (which is fine for me, I learned to respect this culture). So, when a new version of some popular framework or tool comes out, there's a very real risk that the previous version will be abandoned really soon and left without support from developers and community (I was burned by it quite a few times). So no, had to move forward like everyone else.

[pitaj]

That's total BS. Even if it was abandoned, it was already in a stable state with no significant bugs. It wouldn't just cease to be supported. Your workflow wouldn't have to change. And losing a customer over it? That sounds like complete incompetence on your behalf, which your customer probably figured out. Even assuming that Babel 5 would be abandoned, why move to Babel 6 so quickly instead of waiting a month or so while the nice guides, gulp plugins, etc are made?

Your whole situation and outlook really seems to be blaming anything but yourself for mistakes that you made.