Evaluation and Implementation of the Xwalk (Crosswalk) Feature in AEM

[samuelecalamita]

We need to evaluate the Crosswalk (Xwalk) feature and subsequently implement a starter template in our boilerplate for Xwalk projects. see also here

[samuelecalamita]

Boilerplate: https://github.com/diva-e-aem/xwalk-boilerplate

[samuelecalamita]

The doc based and xwalk boilerplates are quite similar with just some differences in a few lines of code and files (see pull request). We want to extend the cli so that we can generate either a xwalk or a doc based boilerplate.

• branching from eds-boilerplate-generator
• rewrite the cli so that it can be possible to generate a xwalk or a doc based project

[samuelecalamita]

hi @mbehzad i've heard that you would like to continue on this topic. If you want have a look in this branch https://github.com/diva-e-aem/eds-boilerplate-generator/tree/18-xwalk-integration and get in touch to me if you need help. Thank you!

[mbehzad]

Hi @samuelecalamita , in doc-based, jest is using jsdom, in the xwalk boilerplate, @happy-dom/jest-environment is used. Does the two boilerplates also need to have different jest setup (+shared part)? Or is currently one jest setup outdated and a single one should work for both? (in the branch is see only jsdom)

[samuelecalamita]

Hi @samuelecalamita , in doc-based, jest is using jsdom, in the xwalk boilerplate, @happy-dom/jest-environment is used. Does the two boilerplates also need to have different jest setup (+shared part)? Or is currently one jest setup outdated and a single one should work for both? (in the branch is see only jsdom)

Hi @mbehzad! One jest setup is definitely outdated. Up to you to choose the right one.