Hi @ShivamVerma380 ,
Looking at the logs:
This has no impact on plugin package deployment but is expected only during plugin development. In Production the plugin package should be registered as a vCenter extension
I suspect you have placed your plugin in "/usr/lib/vmware-vsphere-ui/plugin-packages/". It should be registered as a vCenter Server extension and not present in the plugin-packages folder.
The "libraries" folder should be place in your plugin package and be a part of the plugin zip file. It will be downloaded by the vSphere Client and unpacked in "/etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/".
Best Regards,
Denis
