Install the Open Source metapackage

While PWA uses the standard GraphQL workflow, the metapackage adds capabilities for some PWA Studio features.

You must install this metapackage in all projects using PWA Studio 12.1.0 and higher.

Installation as a git-based composer package#

To set up and develop your PWA extension modules locally, use the following instructions.

1. Clone the magento2-pwa repository into your vendor directory name:

   git clone git@github.com:magento/magento2-pwa.git ext/magento/magento2-pwa
   CopyCopied to your clipboard
   git clone git@github.com:magento/magento2-pwa.git ext/magento/magento2-pwa

2. Update the magento2/composer.json settings to create a better development workflow for your extension modules:

   • Update the minimum-stability for packages to dev. This allows for the installation of development modules:

     composer config minimum-stability dev
     CopyCopied to your clipboard
     composer config minimum-stability dev

   • To work with stable packages, ensure that the prefer-stable property is true. This property should already be included in the composer.json file, right above the minimum-stability setting.

   • Configure composer to find new extension modules. The following command configures composer to treat any extension code inside the ext directory as a package and creates a symlink to the vendor directory:

     composer config repositories.ext path "./ext/*/*/*"
     CopyCopied to your clipboard
     composer config repositories.ext path "./ext/*/*/*"

3. Install the pwa metapackage:

   composer require magento/pwa
   CopyCopied to your clipboard
   composer require magento/pwa

At this point, you should see symlinks for all the pwa modules inside the vendor directory. These symlinks allow you to:

• Run a Magento installation with additional modules.
• Develop locally using the standard git workflow.

You may need to ensure that there are no Magento_PWA* modules listed as enabled when you run bin/magento module:status. If there are, follow the docs on how to enable modules.

Setting up the Git workflow#

To improve the developer experience even further, you can add these configurations as well:

1. Exclude all the ext directories in the project's .git configuration:

   echo ext >> ./.git/info/exclude
   CopyCopied to your clipboard
   echo ext >> ./.git/info/exclude

2. Skip your project's root directory composer.\* files to avoid committing them by mistake:

   git update-index --skip-worktree composer.json && git update-index --skip-worktree composer.lock
   CopyCopied to your clipboard
   git update-index --skip-worktree composer.json && git update-index --skip-worktree composer.lock

   NOTE: You can reverse this operation anytime as needed:

   git update-index --no-skip-worktree composer.json && git update-index --no-skip-worktree composer.lock
   CopyCopied to your clipboard
   git update-index --no-skip-worktree composer.json && git update-index --no-skip-worktree composer.lock

Cloud deployment extension installation#

1. Add https://repo.magento.com as a composer repository by adding the following to the composer.json file of your cloud instances.

   "repositories": {
       "repo": {
           "type": "composer",
           "url": "https://repo.magento.com"
       }
   },
   CopyCopied to your clipboard
   1"repositories": {
   2    "repo": {
   3        "type": "composer",
   4        "url": "https://repo.magento.com"
   5    }
   6},

2. Require in magento/magento2-pwa extension by adding the following to the composer.json file of your cloud instances.

   "require": {
       "magento/magento2-pwa": "0.2.1"
   },
   CopyCopied to your clipboard
   1"require": {
   2    "magento/magento2-pwa": "0.2.1"
   3},

3. Ensure your auth.json file has valid credentials for repo.magento.com.

4. Run composer update to update your composer.lock file.

5. Push the changes and deploy your cloud instance.

Last updated 4/28/2022

Was this helpful?

Yes

No