To develop Merchant Center Custom Applications we recommend using the
It's a command-line interface, inspired by
react-scripts to develop and build a React application.
This command starts the application in
development mode. The page will reload if you edit source files.
This command bundles the application in
production mode to the
It also creates an
index.html.template file, which contains references to the generated bundle entry points. This file needs to be compiled to
index.html, based on runtime values. See Production build for more information.
This command compiles the
index.html.template file into an
index.html file, based on the application config. Additionally, it also generates Content Security Policy headers, including SHA hashes based on the runtime configuration. See the Compiling a Custom Application section for more information.
This script requires
mc-scripts build to be executed first.
This feature is available from version
mc-scripts CLI has the dotenv features built-in.
By default, the following dotenv files are loaded according to the current environment values specified on each command:
process.NODE_ENV. The priority of how the files are merged and overwritten goes from top to bottom (highest defined variable overrides lower).
.env.production.local: Local overrides of environment-specific settings.
.env.production: Environment-specific settings.
.env.local: Local overrides. This file is loaded for all environments except test.
Please refer to the dotenv documentation for more details.
Furthermore, you can pass additional dotenv files by using the following option:
--env <path>: Parses the file path as a dotenv file and adds the variables to the environment. Multiple flags are allowed.
These files will take higher priority over the standard environment dotenv files.