Stop, right now, just let it go, take a step back from the bleeding edge and see that you've got all the JavaScript libraries and tools you need to put together any application you could imagine. If your imagination is big enough then you'll be hand writing your own additions in no time. So long as your applications runs on the major browsers latest-1 without issue there isn't a reason to upgrade. If you're writing a project there isn't a reason to make a framework jump, and if Angular 1 to 2 is that different, consider it a framework jump. Why feel bad about not knowing your way around when you go from one framework to another, would you feel the same going from Drupal to Wordpress? They are both CMSs, both PHP, both extended far beyond their initial goals. Angular 1 will go into maintenance if Angular 2 is that different, development will slow, and eventually you'll upgrade to Angular 3, which is incompatible with Angular 2, but after years of having a working application.
I've gone from Angular, to Kendo, to Ember, to Backbone. If you want to make an 'investment' in knowledge of front-end development learn the plain JavaScript, read through the framework you're using. Walk through the execution, that will allow you as a developer-for-hire to pickup the newest shiny on a new team with less issues.
Web development has always had this pace, whatever tool or setup you commit too, the next week someone will call you an idiot for using it. Ignore them, make something maintainable, nothing in the new framework is ever mission critical, just nice to have.