The new version of Angular offers error codes, debugging guides.

SafeValue must use [property]=binding: From now it becomes easier to answer the question of how to debug Angular in visual studio code. On the 20 of January, the Angular JavaScript framework developers released standardized error codes and debugging guides for the platform. The purpose of this was to speed up and simplify the debugging process. The Angular developer's implemented the error codes as a part of Angular 11.1.0. You can now receive the standardized error codes, details, and formatting in the most common error messages. As well, the developers also tried to make the format of the message itself the most convenient. Each error message begins with the NG prefix, which helps differentiate the TypeScript errors and browser messages from specific Angular errors. The error type is indicating by the next number in the message, wherein the runtime errors start from 0 and for the compiler issues reserved number space from 1 to 9. Descriptions of the most common errors and guides for debugging them can be found in the link to angular.io/errors attached to the error message. If you need to realize how to debug Angular application, you can find the answer faster and comfortable. For your convenience, Angular University also posted on YouTube a series of instructional videos. The Angular 11.1.0 point release you can get from GitHub, besides the multitude of bug fixes, offers various performance improvements, new enhancements for the compiler and language service. The new Angular 12 version, expected in May, will contain more improvements to error messaging and ng-linker for distributing Ivy libraries to NPM. (see http://g.co/ng/security#xss)