In the online documentation, guidance is given regarding widgets using a shared 3rd party libraries (Use other JavaScript libraries—Web AppBuilder for ArcGIS | ArcGIS ). What is the deployment story for such a situation?
Presumably, this is also the pattern that should be used for any shared code we wish to refactor out of our widgets—assuming it can be deployed? It appears that some of the 7 or so deployment options Julie Powell previously posted, would not support this. It would be nice if the dependencies expressed by one's widget would cause esri's machinery to include those dependencies in the bits that it vacuums up from your disk and redistribute when and wherever the apps gets deployed. Is there an official position from esri on this?
