Page.js not updating after clientlib change

Hi, 

If you need your JavaScript to load when your component's dialog opens, you can use something like this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/modify-dialog-value-after-dialog-submission-in-aem/m-p/376541 

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
      jcr:primaryType="cq:ClientLibraryFolder"
      categories="cq.authoring.dialog"/>

If you want your JavaScript to load when the Page editor loads, something like the example below should work:

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
      jcr:primaryType="cq:ClientLibraryFolder"
      categories="cq.authoring.editor.sites.page.hook"
      dependencies="cq.authoring.editor.sites.page"/>

If you are trying to override a core component clientlib, you may need to check this: https://www.youtube.com/watch?v=0T9w8XCwtYA

Hope this helps

If this is happening on a test env and not locally one area to look at would be caching as often locally you would not be going via dispatcher etc which could be caching.  You could check this on your test env by appending query string params to the file path which would bypass dispatcher cache and force a load from the AEM instance.

you could enable clientlib versioning which would ensure the JS file path changes if the underlying files which make up the clientlib are modified.

@michaelneu007 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!