The merchant experiences deployment errors when using the Baler module on a production environment, as the feature is currently in the early alpha development stage.
Early-alpha Baler Javascript bundling is not ready for production use and is used at your own risk.
We do not recommend that merchants use the Baler module in a production environment, as it is currently in the early alpha development stage. Using it can result in deployment errors.
Steps to reproduce:
.magento.env.yaml
file, which enables the Baler Javascript bundling package."magento/module-baler": "1.0.0-alpha"
to require
section of composer.json
.Expected result:
Successful deployment.
Actual result:
The merchant sees the following error message in the deployment logs on the cloud, which is <project home>/var/log/cloud.log
, upon the static content deploy stage:
[2020-08-19 12:06:12] WARNING: [1007] Baler JS bundling cannot be used because of the following issues:
[2020-08-19 12:06:12] WARNING: - Path to baler executable could not be found. The Node package may not be installed or may not be linked.
The Baler module is currently in the early alpha development stage, and the Baler extension installation process is complex.
You can review existing Baler Alpha documentation at Github/Magento/Baler/Getting started with the alpha. However, it is not ready for production use, and it is used at your own risk. It is recommended instead that you merge or bundle Javascript (JS) files using Adobe Commerce’s built-in bundling (basic bundling) for file optimization.
php -f bin/magento config:set dev/js/enable_js_bundling 1
To learn more, refer to CSS and Javascript file optimization on Adobe Commerce on cloud infrastructure and Adobe Commerce on-premises.