As many people done, we’ve changed our Angular 1 sites to a component model, so we’re already familiar with how components work. Angular 2 is ALL components, and while it is quite similar, it has some interesting structures and some irritating ones.
Caching Issues for Active Angular Projects.
In the final stages of development, systems that may get quick tweaks in real-time, where a bug has stopped the flow of business and the developer needs to get the fix in place ASAP. The client doesn’t know to hit Ctrl+F5 and his browser is just showing them the same code as they had. You can generally override the browser cache by adding a querystring, but then you have to dig around and get rid of them, or even change them more than once. Here’s a solution.
Replacing $watch capabilities with $onChanges in Angular Components using Typescript
The Angular feature $watch has become known for its tendancy to hog memory, so we’ve been avoiding it wherever we can. However, with Components, the fact that you may only have a few bound values makes it much more necessary to have a watch on a value. There is a very easy way to do this.