Will this not result in invalid HTML, when you have < in an attribute?

To me the option writes out separate lines in the JS. Can you check that?

Also remember AEM is stateless, so there is no session-failover.

Overall I would say, see what you can cache. For example in the browser / dispatcher, after this look at optimizing the code.

This to me looks not like a valid syntax.

I have create an internal ticket for you, reference: CQ-4210433

Sure that is why I requested to raise a support ticket.Indeed my suggestion for the logging is just to hide it.

I don't think the contexts here are shared. So perhaps what you can do is to write JS-vars, and use these in handlebars?

First: Your JSON is invalid, make sure to fix that first.I have made an example on how the deal with this in Javascript.HTL:<ul data-sly-use.jsonprocessing="json.js" data-sly-list="${jsonprocessing.keys}">   <li>${item}</li></ul>Javascript:json.js   use(function () {    var jsondata = currentPage.pr...

Since 6.2 there is no need anymore for obfuscated-apis, just use apis