Destroying the map - memory leak about angular-cli-esri-map

[andygup]

So, some good news is we just added a view.destroy() method in the /next build of the JS API that you can test it out before the next release (4.17 - Early October 2020): https://github.com/Esri/feedback-js-api-next. If you have a chance to test it, let us know how if you run into any issues? I'm going to close out this issue for now.

// Unset map from the view so that it is not destroyed
const map = view.map;
view.map = null;

// Coming in 4.17 - destroy the view and all attached resources
view.destroy();

[andygup]

Take a look at my write-up here: https://community.esri.com/thread/258078-memory-issue-arcgis-414-angular-memory-not-getting-freed#comment-946737. The best practice is create a service that recycles the MapViews and DOM nodes.