woocommerce/plugins/woocommerce-blocks/docs/contributors/contributing/javascript-build-system.md

JavaScript Build System

Table of contents

• Environment variables
• Babel
• External scripts
• Aliases
• Styling
• Relevant files

WooCommerce Blocks uses Webpack to build the files that will be consumed by browsers. There are several different Webpack configs in order to build files for different contexts of the plugin. They can all be found in webpack.config.js, but this is a quick summary:

• CoreConfig: config for shared libraries like settings, blocks data or some HOCs and context.
• MainConfig: config that builds the JS files used by blocks in the editor and is responsible for registering the blocks in Gutenberg.
• FrontendConfig: config that builds the JS files used by blocks in the store frontend.
• PaymentsConfig: config that builds the JS files used by payment methods in the Cart and Checkout blocks.
• ExtensionsConfig: config that builds extension integrations.
• StylingConfig: config that builds CSS files. You can read more about it in the page CSS build system.

Details on each config can be found in webpack-configs.js. Entry points are declared in webpack-entries.js.

Environment variables

Different builds are generated depending on the variable NODE_ENV. It can have two values: production or development. Production builds include tree-shaking, minification and other performance enhancements, while development builds are focused on development and include source maps. You can read more about environment variables in Webpack docs.

Babel

Most of our code is transpiled by Babel. This allows us to use the latest JavaScript technologies without affecting browser support.

Some of the Babel plugins we use can be found in webpack-configs.js.

External scripts

Several scripts are loaded as externals. That means that they can be imported in WooCommerce Blocks as any other package, but instead of being bundled in our built files, they are loaded from an external file provided by WordPress (or Gutenberg, if enabled).

@wordpress/dependency-extraction-webpack-plugin is used to automatize dependency extraction for common WP scripts.

In practice, that means the dependency version is:

• deterministic when running WooCommerce Blocks in isolation (e.g. unit tests). In this case, the dependency will have a version as stated in package.json,
• non-deterministic when run in the WordPress ecosystem. Depending on the WordPress or Gutenberg version the user has installed, the version of external dependencies may also vary.

@wordpress/dependency-extraction-webpack-plugin script is applied to each of the build processes: Core, Main, Frontend, Payments, Extensions.

wordpress-components alias

@wordpress/components is one of the dependencies that gets externalized by the plugin. You can see the external components.min.js file being loaded on the Editor pages containing blocks that depend on the @wordpress/components, while the code is not bundled within WooCommerce Blocks files.

For optimization purposes, there's a wordpress-components alias created, which is used in the frontend code. Thanks to that, the dependency omits the Dependency Extraction Plugin and behaves like any other dependency: it's tree-shaken and only the necessary code is bundled with the block. That allows us to avoid loading the whole @wordpress/components on the frontend pages.

Aliases

There are several aliases for internal imports which make importing files across the file tree easier. Instead of having to write a long relative path, they allow writing an alias:

-import { useStoreCartCoupons } from '../../../../base/hooks';
+import { useStoreCartCoupons } from '@woocommerce/base-context/hooks';

Aliases also ease refactors because imports no longer depend on the exact location of the file.

All available aliases can be found in webpack-helpers.js.

Styling

CSS builds follow a separate path from JS builds, more details can be found in the CSS build system.

Relevant files

Webpack config is split between several files:

• webpack.config.js: Top level webpack config.
• bin/webpack-configs.js: Code for generating each build config. This most closely resembles a classic webpack config - if you're looking for something, start here.
• bin/webpack-entries.js: Code for generating webpack entry definitions and mapping source files to entry points. If you're adding a new block or module to the build, start here.
• bin/webpack-helpers.js: Includes utils to load external code at run time, e.g. some dependencies from Woo and WordPress core.

---

We're hiring! Come work with us!

🐞 Found a mistake, or have a suggestion? Leave feedback about this document here.