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

JavaScript Build System

Table of contents

• Environment variables
• Babel
• External scripts
• Aliases
• Styling
• Legacy builds
• 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.
• 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 are imported in WC Blocks as any other package, but instead of being bundled in our built files, they are loaded from an external file. We use @wordpress/dependency-extraction-webpack-plugin to automatize dependency extraction for common WP scripts.

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.

Legacy builds

In the past, when building WC Blocks, special builds targeting old versions of WordPress were generated. Those builds were named 'legacy builds' and might have a smaller set of blocks available. For example, All Products and Filter blocks were not available on WP 5.2.

There were legacy builds of the MainConfig, FrontendConfig and StylingConfig. Currently, those builds are no longer generated since WC Blocks doesn't support WP 5.2 anymore, but the built system is still in place in case legacy builds are needed in the future.

Relevant files

Webpack config is split between several files:

• webpack.config.js: Top level webpack config. Includes support for legacy and main build.
• 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.