@magento run all tests

Hello @Amadeco,

Thanks for the contribution!

We request you to please provide us with some more details on the replacement of jarallax with jarallax-wrapper. We can pick this PR as a feature request. But we need this information to proceed.

Thanks

Hello,

At the time, I was using a bundler for production (https://github.com/magesuite/magepack) to manage JavaScript files. This issue is isolated to that setup.

When I compiled the files, the jarallax object was not defined, likely due to a context issue or the way the bundler handles modules (specifically, the order of the JS files).

Magento provide the jarallax-wrapper module to call the jarallax class and attach it to the window (global) object, which is why I submitted this issue in the first place to solve mine.

But the ways the requirejs-config file is declared (shim), Magento_PageBuilder/js/resource/jarallax/jarallax-video would be sufficient :

shim: {
    'Magento_PageBuilder/js/resource/jarallax/jarallax-video': {
        deps: ['jarallax-wrapper', 'vimeoWrapper']
    }
}

(it would be great to load vimeoWrapper and vimeo only on demand too)

Nowadays, with HTTP/2 and HTTP/3, bundlers are not always ideal for frontend performance which generate big JS files. It's up to you to decide whether addressing this is still relevant.

@magento create issue

Hello @Amadeco,

Thanks for the detailed explanations!

It seems the issue occurs due to the third-party extension i.e. https://github.com/magesuite/magepack not from the core Magento 2. We request you to please use the default Magento's JS Bundler:

https://developer.adobe.com/commerce/frontend-core/guide/themes/js-bundling/

And let us know if you are still able to reproduce the issue.

Thanks

Hello @Amadeco,

Have you had a chance to look into this #865 (review)?

Thanks