Its just about adding clientlib like what is mentioned in the doc in your custom script rather than OOTB headlibs but the flag to use defer is OOTB. You just need to add it in your script where you are loading clientlibs

Here is an article which talks about same requirement. Could possibly give this a shot. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/find-unused-assets-in-aem/m-p/174281

Take a look at https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2412.. There is a likely solution that you can give a try..

By any chance do you have any IP whitelisting on SFTP. When you connect from your laptop, it would be trying to access FTP from your IP, whereas in Managed Instance, it would be trying to access from IP of Managed AEM Author?

Java being backward compatible, I dont think you would see any major issues upgrading from Java 8 to Java 11.

This is great... Will be very helpful for the ones who use SPA goign forward

Yeah. we had to change those links to normal links rather than React link..

Yeah, my question originated from that documentation only.. Just that I do not want to fix it to start from 2.0 or something.. OOTB one that starts from 1.0 and then increments by .1 normally and .x.1 when we revert and start a new tree is fine.. But is there an OOTB option to do version bump by aut...

Hi guys, When we create versions of the page, it starts from 1.0 and then increments to 1.1, 1.2. Is there a limit on how much this 1.x can go to.If I am making a major change, can I make it 2.0 and then let it increment from there on?

The URL modification happens at client side before it reaches Dispatcher. For "#" in the URL, we were facing this issue consistently but query params, it was intermittent.