@kautuk_sahni Any POC who can help on Target and Adobe I/O for this question ? 

I agree with @Bhuwan_B  and @Rohit_Utreja , your best bet here is to create a clientLib specific for your component dialog including those JS which you need and then loading it to the dialog via extraClientLibs . ThanksVeena ✌

@AEM_Forum The link @Jaideep_Brar gave you will tell you the complete picture of Headless AEM . May be you have to start from her https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/content-services/overview.html?lang=en#content-services . Let me try an...

@fionas76543059 Yes you can have it. That is exactly why we use categories for. What AEM does is, it will compile all the files in the same categories to a single JS or CSS file and include it wherever that category is referred.  Let us say you have scenario where you are using same category name fo...

As Jorg told , I don't think it is a valid dependency. Your project should build fine , if you remove it I believe. 

@vinodprathipati Can you check the node of the page where you have authored the experience fragment (XF) , and check if the property is rightly reflecting ? If not re-publish the content page (not XF) and check if it solving. It can only be a content issue as far as I could understand.

@Vaibhavi_J I doubt , if the page reloads before the Dialog is submitted, the changes will not be saved right ?

I might have to try this to give you exact code. If you are good in Jquery just do some trial and error and you should be able to figure that out I believe. Else I might need some time to check this to get you the exact code.

try document.createElement('coral-alert')

Not sure if you are looking for something like this https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/reference-materials/coral-ui/coralui3/Coral.Alert.html