Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

reposition site.js script call

Avatar

Level 2

Hi Everyone,

 

is there a way in AEM to reposition the site bundle that is generated.

 

right now it always is injected before some of my client lib dependencies

 

<script src="/etc.clientlibs/bhn/clientlibs/clientlib-site.lc-ebe67a9fbbfc94e400de1cb2bd2c66a9-lc.min.js"></script>


regards

Dev

1 Accepted Solution

Avatar

Correct answer by
Level 5

 

  • Check the Inclusion Source:

    • Identify where the site clientlibs are being included from. Typically, this is done in the template page policy and included by the core page component in footer.html.

narendiran100_0-1724346272692.png

 

  • Modify the Inclusion:

    • If the site clientlibs are loaded from the page policy, remove them from there.
    • Add the site clientlibs (both JS and CSS) in customheaderlibs.html and customfooterlibs.html after your dependencies, clientlibs are injected.
  • Additionally, you can add the required clientlibs as dependencies to the site clientlibs in the ui.frontend project config file -ui.frontend/clientlib.config.js. The aem-clientlib-generator uses this config file. 
  • narendiran100_1-1724346620225.png

     

 

 

View solution in original post

4 Replies

Avatar

Community Advisor

Hi,

 

Are you asking if you could place the script in a different part of the document? If so, absolutely yes. You just need to identify which "page" component you are using. From there, you will see a series of "files" being included. For example:

1. My "page" component inherits from core/wcm/components/page/v3/page.

2. This component has the Page.html file, which includes head.html.

EstebanBustamante_0-1724344153992.png

 

3. The head.html file includes customheaderlibs.html (which is most likely part of your page component).

EstebanBustamante_1-1724344188139.png

 

If you need to place it elsewhere, you could, for example, overlay the head.html file and move your scripts where needed.

 

 

Hope this helps!



Esteban Bustamante

Avatar

Community Advisor

Hi @devendrabhn ,

Try to keep clienlibs js in footer & ensureit is last in the order

Use defer and async attributes on site.js which may also some extent ensure delay
<meta data-sly-call="${clientLib.js @ categories='your.clientlib', loading='defer'}" data-sly-unwrap></meta>

Refernce:- https://github.com/nateyolles/aem-clientlib-async

 

Apart from that  setTimeout or setInterval is another way 

const intervalId = setInterval(() => {
console.log("This will be logged every 2 seconds");
}, 2000);

// To stop the interval
clearInterval(intervalId);

 

Thanks

 

Avatar

Correct answer by
Level 5

 

  • Check the Inclusion Source:

    • Identify where the site clientlibs are being included from. Typically, this is done in the template page policy and included by the core page component in footer.html.

narendiran100_0-1724346272692.png

 

  • Modify the Inclusion:

    • If the site clientlibs are loaded from the page policy, remove them from there.
    • Add the site clientlibs (both JS and CSS) in customheaderlibs.html and customfooterlibs.html after your dependencies, clientlibs are injected.
  • Additionally, you can add the required clientlibs as dependencies to the site clientlibs in the ui.frontend project config file -ui.frontend/clientlib.config.js. The aem-clientlib-generator uses this config file. 
  • narendiran100_1-1724346620225.png