Trying to register previous cmp as Amasty_Xsearch/js/wrapper, but previous define was async and not yet resolved. Make sure all of unknown dependencies of previous cmp are listed in "import" section of breeze_default.xml

[kostyastr8]

Hello, can you help me with this
I am getting this error, and I'm not sure what I should do with this . We don't have any JS customization or additional implementation
The same is related to slick and jQuery.. I installed this additional breeze amsty promo , but after that I got this error

[IbrahimS2]

Please share the latest version of the Amasty Search module so I can look into it further.

[kostyastr8]

@IbrahimS2
frontend.zip

[kostyastr8]

@IbrahimS2, what about the xsearch issue ?? I see another one :

Appear when you are loading the page, and then open the console (it is also inside xsearch js )

[vovayatsyuk]

Looks like a race-condition bug in Breeze. Will try to reproduce it locally.

[vovayatsyuk]

Try disabling jsmerge/bundling as a workaround.

bin/magento config:set dev/js/merge_files 0 && bin/magento config:set dev/js/enable_js_bundling 0

[vovayatsyuk]

I've just tagged swissup/module-breeze:2.24.9. It should fix the issue!

[vovayatsyuk]

Looks like an unfinished integration of Amasty_Promo causes this issue. I've just commented code that doesn't work and cause the errors:

breezefront/module-breeze-amasty-promo@87cb9df

[IbrahimS2]

@vovayatsyuk Can we ship Slick as a core component so it is available, especially if the Pagebuilder Slider relies on Slick natively?

[vovayatsyuk]

Our pagebuilder slider is not Slick-based. We use our slider implementation, which is based on native snap-scroll styles.

[IbrahimS2]

@vovayatsyuk No, I mean that the Magento native Pagebuilder Slider uses that, from what I know.

But anyway, I think the idea is sound; what do you think?

[vovayatsyuk]

I don't like the idea of including a slider library.

I can only imagine the Slick "facade" inside breeze - a skinny class that mimics Slick API. So you can include a third-party class and everything works (but it's not using Slick under the hood):

define(['slick'], (Slick) => ...) // Slick is not a slick here, but can do a lot of similar things

But the issue is third-party vendors do not reuse Slick from Magento, they bring their own copies:

define(['Vendor_Module/js/slick'], (Slick) => ...)

Because of this you will still need to write integration.

[IbrahimS2]

I agree — there's no need to include the Slick library by default. If someone wants to use it, they can take the initiative to integrate it into their build.

However, if we can create a Slick facade that mimics the Slick API, it would make third-party integrations much easier. We could map their usage to our built-in solution, reducing complexity and minimising the need for additional dependencies.