{"id":346167,"date":"2022-07-29T12:32:49","date_gmt":"2022-07-29T12:32:49","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=346167"},"modified":"2022-07-29T12:32:58","modified_gmt":"2022-07-29T12:32:58","slug":"js-bundling-in-magento2","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/js-bundling-in-magento2\/","title":{"rendered":"Js bundling in Magento2"},"content":{"rendered":"\n

In this article, We will learn about Magento JS Bundling and Advanced JS Bundling.<\/p>\n\n\n\n

What is Javascript bundling?<\/h2>\n\n\n\n

Javascript bundling is an optimization technique that is used in today\u2019s module-based development to group individual files to decrease the number of HTTP requests which are needed to load a page. This is acquired by merging multiple JavaScript files together into one file. Besides, it denies the main advantage of using module loaders such as RequireJS which is loading files asynchronously.<\/p>\n\n\n\n

Enable bundling<\/h2>\n\n\n\n

1) . From the installation directory, switch to production mode:<\/p>\n\n\n\n

bin\/magento deploy:mode:set production<\/pre>\n\n\n\n
2).Enable JavaScript bundling<\/p>\n\n\n\n
bin\/magento config:set dev\/js\/enable_js_bundling 1<\/pre>\n\n\n\n
3). Optimize bundling by minifying JavaScript files:<\/p>\n\n\n\n
bin\/magento config:set dev\/js\/minify_files 1<\/pre>\n\n\n\n
4).Enable cache busting on static file URLs. This ensures users get the latest version of the assets anytime they update:<\/p>\n\n\n\n
bin\/magento config:set dev\/static\/sign 1<\/pre>\n\n\n\n
5). To configure JavaScript bundling, you must disable Javascript file merging. Bundling will not work as the merging of files excludes bundling:<\/p>\n\n\n\n
bin\/magento config:set dev\/js\/merge_files 0<\/pre>\n\n\n\n
6). bin\/magento setup:static-content:deploy<\/p>\n\n\n\n
7). Finally, clear the cache:<\/p>\n\n\n\n
bin\/magento cache:clean config<\/pre>\n\n\n\n
How bundling works<\/h2>\n\n\n\n
Magento 2 JS Bundling mechanism works to combine all the javascript bundles into some few javascript bundles and loaded for all the pages. Page rendering is blocked until the browser downloads all the bundles synchronously. Each bundle should be at least 100KB as per the Magento Standard.<\/p>\n\n\n\n
To make it easier to use, you can also exclude the specific file that could not be processed in bundling using etc\/view.xml.<\/p>\n\n\n\n
The following code snippet from Luma theme<\/a> shows the types of files you should exclude from the bundling process.<\/p>\n\n\n\n
<exclude>\n    <item type="file">Lib::jquery\/jquery.min.js<\/item>\n    <item type="file">Lib::jquery\/jquery-ui-1.9.2.js<\/item>\n    <item type="file">Lib::jquery\/jquery.ba-hashchange.min.js<\/item>\n    <item type="file">Lib::jquery\/jquery.details.js<\/item>\n    <item type="file">Lib::jquery\/jquery.details.min.js<\/item>\n    <item type="file">Lib::jquery\/jquery.hoverIntent.js<\/item>\n    <item type="file">Lib::jquery\/colorpicker\/js\/colorpicker.js<\/item>\n    <item type="file">Lib::requirejs\/require.js<\/item>\n    <item type="file">Lib::requirejs\/text.js<\/item>\n    <item type="file">Lib::date-format-normalizer.js<\/item>\n    <item type="file">Lib::legacy-build.min.js<\/item>\n    <item type="file">Lib::mage\/captcha.js<\/item>\n    <item type="file">Lib::mage\/dropdown_old.js<\/item>\n    <item type="file">Lib::mage\/list.js<\/item>\n    <item type="file">Lib::mage\/loader_old.js<\/item>\n    <item type="file">Lib::mage\/webapi.js<\/item>\n    <item type="file">Lib::mage\/zoom.js<\/item>\n    <item type="file">Lib::mage\/translate-inline-vde.js<\/item>\n    <item type="file">Lib::mage\/requirejs\/mixins.js<\/item>\n    <item type="file">Lib::mage\/requirejs\/static.js<\/item>\n    <item type="file">Magento_Customer::js\/zxcvbn.js<\/item>\n    <item type="file">Magento_Catalog::js\/zoom.js<\/item>\n    <item type="file">Magento_Ui::js\/lib\/step-wizard.js<\/item>\n    <item type="file">Magento_Ui::js\/form\/element\/ui-select.js<\/item>\n    <item type="file">Magento_Ui::js\/form\/element\/file-uploader.js<\/item>\n    <item type="file">Magento_Ui::js\/form\/components\/insert.js<\/item>\n    <item type="file">Magento_Ui::js\/form\/components\/insert-listing.js<\/item>\n    <item type="directory">Magento_Ui::js\/timeline<\/item>\n    <item type="directory">Magento_Ui::js\/grid<\/item>\n    <item type="directory">Magento_Ui::js\/dynamic-rows<\/item>\n    <item type="directory">Magento_Ui::templates\/timeline<\/item>\n    <item type="directory">Magento_Ui::templates\/grid<\/item>\n    <item type="directory">Magento_Ui::templates\/dynamic-rows<\/item>\n    <item type="directory">Magento_Swagger::swagger-ui<\/item>\n    <item type="directory">Lib::modernizr<\/item>\n    <item type="directory">Lib::tiny_mce<\/item>\n    <item type="directory">Lib::varien<\/item>\n    <item type="directory">Lib::jquery\/editableMultiselect<\/item>\n    <item type="directory">Lib::jquery\/jstree<\/item>\n    <item type="directory">Lib::jquery\/fileUploader<\/item>\n    <item type="directory">Lib::css<\/item>\n    <item type="directory">Lib::lib<\/item>\n    <item type="directory">Lib::extjs<\/item>\n    <item type="directory">Lib::prototype<\/item>\n    <item type="directory">Lib::scriptaculous<\/item>\n    <item type="directory">Lib::less<\/item>\n    <item type="directory">Lib::mage\/adminhtml<\/item>\n    <item type="directory">Lib::mage\/backend<\/item>\n<\/exclude><\/pre>\n\n\n\n
In this way, we can exclude some scripts from the bundle but can\u2019t decide to load only page-specific bundles and this is the reason why it takes time to load the mini-cart data or other checkout related data after finishing the page load.<\/p>\n\n\n\n
It also somewhat affects increasing the bundle\u2019s file size while enabling Minifying\/Merging JS in the backend. When we allow the Minify JS option in the backend, it turns out the file (bundle0.min.js) is 8 MB.<\/p>\n\n\n\n
Magento JS Bundling increases the file size of the bundle and uses the alternate option for bundling Advanced JS Bundling. In logical terms, it is somewhat right why we load unnecessary all JS, which is mostly not required for specific pages.<\/p>\n\n\n\n
Advanced Bundling JS<\/h2>\n\n\n\n
Advanced Bundling combines all the packages and serves them in one box. It boosts speed performance and reduces server requests and bundle size for each page loaded in the browser.<\/p>\n\n\n\n
To use Advanced Bundling JS, we have to build bundles for each page, especially those necessary, like the Home page, Category Page, Product Page, Cart, and Checkout Page.<\/p>\n\n\n\n
For example, you might end up with a bundle for the dependencies common to all pages, a bundle for CMS-only pages, a bundle for Catalog-only pages, another bundle for Search-only pages, and a bundle for Checkout pages.<\/p>\n\n\n\n
Required tools<\/h2>\n\n\n\n
The following steps require you to install and have familiarity with the following tools:<\/p>\n\n\n\n