Does breeze compatibility create merged JS files?

[itsrcrowell]

Hey guys,

Once Breeze compatibility is enabled, will it generate those merged JS files? Is that expected behavior? For instance, we have the Amasty Shopby module, and Breeze compatibility is enabled by default. It generated a merged file that stores a couple of JS definitions for this module

[vovayatsyuk]

Do you mean requirejs-config-breeze.js? Yes, better compatibility includes requirejs-configs to get all information about js setup of the modules.

[itsrcrowell]

@vovayatsyuk Magento creates a merged js file like this: merged/da026eb2e7c30c176f74405b18baa143.min.js. Is that the expected behavior for the breeze compatibility?

[vovayatsyuk]

I don't know. I didn't test it with enabled merge option :) Do you have some issues when merge is enabled?

[vovayatsyuk]

Just tested. No, it doesn't merged for me. I don't see anything merged when using breeze.

[itsrcrowell]

That is odd, we're using this setup:
'js' => [
'merge_files' => '1',
'enable_js_bundling' => '0',
'minify_files' => '1',
'move_script_to_bottom' => '1'
],
'css' => [
'merge_css_files' => '1',
'minify_files' => '1',
'use_css_critical_path' => '1'
]

When I disable the breeze compatibility for the amasty shopby extension, the merged file looks like that:

I was wondering whether there is a way to avoid this approach

[itsrcrowell]

I figured it out, I was enabling the compatibility where it wasn't needed that's why breeze was generating the merged file ;(function(require){})(require);