BB-25538: PNPM Package Manager (#41420)

* BB-25540: Create PNPM workspaces configuration and establishing assets build
- add public hoist dependencies
- update root gitignore
- update webpack deps
- update pnpm lock
- update pnpm lock
- update webpack config
- init root PNPM
- add PNPM workspaces
- add sub deps for applications
- update lock
- add pnpm check
- no-lockfile

Co-authored-by: Valerii Yustyniuk <[email protected]>
Co-authored-by: orocrmdeployer <[email protected]>
Co-authored-by: Valerii Yustyniuk <[email protected]>
Co-authored-by: Daria Hanzenko <[email protected]>
Co-authored-by: Andrii Yatsenko <[email protected]>

Author: 5 people

backend/configuration/yaml/bundles-config.rst

@@ -446,8 +446,8 @@ The default configuration for extension with alias "oro_asset":
         # Path to NodeJs executable
         nodejs_path:          ~
 
-        # Path to NPM executable
-        npm_path:             ~
+        # Path to PNPM executable
+        pnpm_path:             ~
 
         # Assets build timeout in seconds, null to disable timeout
         build_timeout:        null

backend/setup/dev-environment/docker-and-symfony/index.rst

@@ -21,7 +21,7 @@ Set Up the Environment
 
 **Development Stack**
 
--  PHP, Composer, Node.js, and NPM should be installed locally for a better development experience.
+-  PHP, Composer, Node.js, NPM and PNPM should be installed locally for a better development experience.
 -  |Symfony Local Web Server| is used to make you more productive while
    developing applications. This server is not intended for production
    use. It supports HTTP/2, TLS/SSL, automatic generation of security

backend/setup/dev-environment/mac.rst

@@ -28,20 +28,26 @@ Environment Setup
       brew install [email protected] composer node
       echo 'export PATH="/usr/local/opt/[email protected]/bin:$PATH" \nexport PATH="/usr/local/opt/[email protected]/sbin:$PATH" \nexport PATH="/usr/local/opt/node@20/bin:$PATH"' >> ~/.bash_profile
 
-4. If you going to use an Enterprise Edition of the application, install and enable the mongodb php extension:
+4. Install PNPM 10 Using NPM:
+
+   .. code-block:: none
+
+        npm install -g pnpm@latest-10
+
+5. If you are going to use an Enterprise Edition of the application, install and enable the mongodb php extension:
 
    .. code-block:: none
 
       pecl install mongodb
       echo "extension=\"mongodb.so\"" >> /usr/local/etc/php/8.4/php.ini
 
-5. Configure PHP:
+6. Configure PHP:
 
    .. code-block:: none
 
       echo "memory_limit = 2048M \nmax_input_time = 600 \nmax_execution_time = 600 \nrealpath_cache_size=4096K \nrealpath_cache_ttl=600 \nopcache.enable=1 \nopcache.enable_cli=0 \nopcache.memory_consumption=512 \nopcache.interned_strings_buffer=32 \nopcache.max_accelerated_files=32531 \nopcache.save_comments=1" >> /usr/local/etc/php/8.4/php.ini
 
-6. Install Symfony Server and enable TLS:
+7. Install Symfony Server and enable TLS:
 
    .. code-block:: none
 
@@ -50,7 +56,7 @@ Environment Setup
       source ~/.bash_profile
       symfony local:server:ca:install
 
-7. Restart the terminal and web browser to get them ready.
+8. Restart the terminal and web browser to get them ready.
 
 What's Next
 -----------

backend/setup/dev-environment/ubuntu.rst

@@ -40,7 +40,13 @@ Environment Setup
       curl -sL https://deb.nodesource.com/setup_22.x | sudo -E bash -
       sudo apt -y install nodejs
 
-4. Install Docker and Docker Compose:
+4. Install PNPM Using NPM:
+
+   .. code-block:: none
+
+        npm install -g pnpm@latest-10
+
+5. Install Docker and Docker Compose:
 
    .. code-block:: none
 
@@ -62,15 +68,15 @@ Environment Setup
 
    For more information, see |Docker installation|.
 
-5. Install Composer v2:
+6. Install Composer v2:
 
    .. code-block:: none
 
       php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');" && php composer-setup.php
       php -r "unlink('composer-setup.php');"
       sudo mv composer.phar /usr/bin/composer
 
-6. Install Symfony Server and enable TLS:
+7. Install Symfony Server and enable TLS:
 
    .. code-block:: none
 
@@ -80,7 +86,7 @@ Environment Setup
       source ~/.bashrc
       symfony server:ca:install
 
-7. Restart the terminal and web browser to get them ready.
+8. Restart the terminal and web browser to get them ready.
 
 
 .. admonition:: Business Tip

backend/setup/dev-environment/windows.rst

@@ -84,15 +84,21 @@ Environment Setup
       curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
       sudo apt -y install nodejs
 
-9. Install Composer:
+9. Install PNPM 10 Using NPM:
+
+   .. code-block:: none
+
+        npm install -g pnpm@latest-10
+
+10. Install Composer:
 
    .. code-block:: none
 
       php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');" && php composer-setup.php
       php -r "unlink('composer-setup.php');"
       sudo mv composer.phar /usr/bin/composer
 
-10. Install Symfony Server:
+11. Install Symfony Server:
 
     .. code-block:: none
 
@@ -116,7 +122,7 @@ Environment Setup
        :alt: Importing certificate to Chrome
 
 
-11. Configure the network. WSL 2 changes the way networking is configured compared to WSL 1. You need to enable proxy of traffic to permit the traffic through the Windows firewall.
+12. Configure the network. WSL 2 changes the way networking is configured compared to WSL 1. You need to enable proxy of traffic to permit the traffic through the Windows firewall.
 
     Run in Ubuntu ``ip addr | grep eth0`` to see the IP address of the WSL 2 virtual machine.
 
@@ -145,7 +151,7 @@ Environment Setup
     .. image:: /img/backend/setup/wsl/firewall-6.png
        :alt: Configure Windows Defender Firewall step 6
 
-12. Restart the terminal and the web browser to get them ready.
+13. Restart the terminal and the web browser to get them ready.
 
 What's Next
 -----------

backend/setup/system-requirements/index.rst

@@ -87,7 +87,7 @@ Oro applications are compatible with most web servers with PHP support, but the
 | *Process Control* | * |Supervisor|  or alternative                    |
 +-------------------+---------------------------------------------------+
 | *Assets*          | * |Node.js| >=22                                  |
-|                   | * |NPM| >10                                       |
+|                   | * |PNPM| >10                                      |
 |                   |                                                   |
 |                   | Used for JS assets minification and SCSS assets   |
 |                   | build.                                            |

backend/setup/upgrade-source-code.rst

@@ -5,10 +5,10 @@
 
 .. _upgrade-to-6:
 
-Upgrade the Source Code to v6.1
+Upgrade the Source Code to v7.0
 ===============================
 
-This guide covers the complete process of upgrading your codebase to OroCommerce v6.1, including dependency updates and code migration.
+This guide covers the complete process of upgrading your codebase to OroCommerce v7.0, including dependency updates and code migration.
 
 .. tip:: If you are looking for instructions on upgrading the entire OroCommerce application rather than just the source code, please refer to our guide on :ref:`Upgrading the Application to the Next Version <upgrade-application>`.
 
@@ -55,6 +55,7 @@ Next, run the following commands:
 
    rm -rf var/cache/*
    rm -rf public/bundles/*
+   rm -rf ./node_modules
    php bin/console assets:install
    php bin/console oro:theme:migrate
 

backend/setup/upgrade-to-new-version.rst

@@ -70,16 +70,22 @@ To retrieve a new version and upgrade your Oro application instance, execute the
 
        rm -rf var/cache/prod/
 
-9. Set up your project source code with Composer.
+9. Remove old JS packages
+
+   .. code-block:: none
+
+       rm -rf ./node_modules
+
+10. Set up your project source code with Composer.
 
    .. code-block:: none
 
        composer install --prefer-dist --no-dev
 
-10. Refer to the ``UPGRADE.md`` and ``CHANGELOG.md`` files in the application repository for a list of changes in the code that
+11. Refer to the ``UPGRADE.md`` and ``CHANGELOG.md`` files in the application repository for a list of changes in the code that
     may affect the upgrade of some customizations.
 
-11. Upgrade the platform.
+12. Upgrade the platform.
 
     .. code-block:: none
 
@@ -105,7 +111,7 @@ To retrieve a new version and upgrade your Oro application instance, execute the
 
                    * **For patch upgrades (minor updates within the same LTS):** While not mandatory, it is **highly recommended** to run search reindexation to ensure the Elasticsearch index structure remains correct.
 
-12. Remove the caches.
+13. Remove the caches.
 
     .. code-block:: none
 
@@ -118,7 +124,7 @@ To retrieve a new version and upgrade your Oro application instance, execute the
         rm -rf var/cache/prod/
         php bin/console cache:warmup --env=prod
 
-13. Enable cron.
+14. Enable cron.
 
     .. code-block:: none
 
@@ -130,13 +136,13 @@ To retrieve a new version and upgrade your Oro application instance, execute the
 
         */1 * * * * /usr/bin/php <application-root-folder>/bin/console --env=prod oro:cron >> /dev/null
 
-14. Switch your application back to the normal mode from the maintenance mode.
+15. Switch your application back to the normal mode from the maintenance mode.
 
     .. code-block:: none
 
         php bin/console lexik:maintenance:unlock --env=prod
 
-15. Run the consumer(s).
+16. Run the consumer(s).
 
     .. code-block:: none
 

bundles/platform/AssetBundle/commands.rst

@@ -22,10 +22,6 @@ The assets can be build only for a specific theme if its name is provided as an
 
     php bin/console oro:assets:build default
 
-.. code-block:: none
-
-    php bin/console oro:assets:build blank
-
 .. code-block:: none
 
     php bin/console oro:assets:build admin.oro
@@ -84,11 +80,11 @@ The ``--force-warmup`` option can be used to warm up the asset-config.json cache
 
     php bin/console oro:assets:build --force-warmup
 
-The ``--npm-install`` option can be used to reinstall npm dependencies in vendor/oro/platform/build folder. It may be required when node_modules contents become corrupted:
+The ``--pnpm-install`` option can be used to reinstall npm dependencies in vendor/oro/platform/build folder. It may be required when `node_modules` contents become corrupted:
 
 .. code-block:: none
 
-    php bin/console oro:assets:build --npm-install
+    php bin/console oro:assets:build --pnpm-install
 
 The ``--skip-css``, ``--skip-js``, ``--skip-babel``, ``--skip-sourcemap``, ``--skip-rtl`` and ``--skip-svg`` options allow to skip building CSS and JavaScript files, skip transpiling Javascript with Babel, skip building sourcemaps, skip building RTL styles and skip building SVG sprite respectively:
 
@@ -161,7 +157,7 @@ You may run individual steps if necessary as follows:
 
 .. code-block:: none
 
-    php bin/console oro:assets:build --npm-install
+    php bin/console oro:assets:build --pnpm-install
 
 The ``--force-debug`` option will launch the child commands in the debug mode (be default they are launched with ``--no-debug``):
 

bundles/platform/AssetBundle/index.rst

@@ -203,7 +203,7 @@ Detailed information about JS modules configuration is available in the :ref:`JS
 Configuration Reference
 -----------------------
 
-AssetBundle defines the configuration for NodeJs and NPM executable.
+AssetBundle defines the configuration for NodeJs and PNPM executable.
 
 All these options are configured under the `oro_asset` key in your application configuration.
 
@@ -225,12 +225,12 @@ nodejs_path
 
 Path to NodeJs executable.
 
-npm_path
-^^^^^^^^
+pnpm_path
+^^^^^^^^^
 
 **type: `string` required, default: found dynamically**
 
-Path to NPM executable.
+Path to PNPM executable.
 
 build_timeout
 ^^^^^^^^^^^^^
@@ -239,12 +239,12 @@ build_timeout
 
 Assets build timeout in seconds, null to disable the timeout.
 
-npm_install_timeout
-^^^^^^^^^^^^^^^^^^^
+pnpm_install_timeout
+^^^^^^^^^^^^^^^^^^^^
 
 **type: `integer` required, default: `null`**
 
-Npm installation timeout in seconds, null to disable the timeout.
+PNPM installation timeout in seconds, null to disable the timeout.
 
 webpack_dev_server
 ^^^^^^^^^^^^^^^^^^
@@ -305,6 +305,20 @@ To fix the error, remove an application cache and warm it up:
     rm -rf var/cache/*
     php bin/console cache:warmup
 
+**PNPM not found**
+
+Appears after migration to `PNPM`.
+
+To fix the error, install `pnpm`, remove the existing node modules and re-build the assets:
+
+.. code-block:: none
+
+    npm install -g pnpm
+    rm -rf ./node_modules
+    php bin/console cache:clear
+    php bin/console oro:assets:build
+
+
 **Error: "output" for "assets" group in theme "oro" is not defined**
 
 Please follow |AssetBundle upgrade documentation| to update `assets.yml` files according to new requirements.