Announcing availability of the Page Diagnostics Tool for SharePoint

Hi wbaer,

Thanks for delivering this tool, we as a SharePoint solution editor company will probably rely on it to increase performance and user feedback on custom SharePoint portals we develop. 

A quick technical feedback though, we experience conflicts when the plugin is installed because it double loads some SharePoint standard JS libraries (SP.js, SP.runtime.js and SP.publishing.js) which sometimes already are on the page/masterpage and I found two drawbacks :

- they are loaded from [the current SharePoint site]/_layouts/15/*.js rather than the CDN

- they break something when custom code is executing a SP.clientcontext query and gathering fields with some SP.Taxonomy.TaxonomyField among them. The taxonomy fields are then badly initialized and all their properties are null. 

I can confirm that if I prevent the plugin from loading SP.js and SP.runtime.js and directly use the ones previously loaded from static.sharepointonline.com CDN it works seamlessly. My advice would be to check the availability of both the namespaces registered by these JS files and call $.getscript() only if needed.