Initializing JS components after loading offers | Community
Skip to main content
New Participant
December 20, 2021
Solved

Initializing JS components after loading offers

  • December 20, 2021
  • 1 reply
  • 943 views

We are using Target loaded by Launch and consider using Target's Visual Composer with Experience Fragments exported from AEM. We also have quite a lot of components with custom JS initialization code which will be used in these fragments if we start using them.

What is the recommended way of calling this initialization right after an offer with a component is loaded? What event should our code handle to achieve this, if we don't know exactly when the offer will be loaded? Also, what will change in the approach if Launch's script is loaded with "async" or "defer"?

Our current Target version is 1.8.7.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Alexander_Prikhodko

Sorry for the confusion, our at.js version is actually 1.8.2.

1 reply

Alexander_PrikhodkoAuthorAccepted solution
New Participant
December 21, 2021

Sorry for the confusion, our at.js version is actually 1.8.2.