The `ember-cli-deploy-build` package is a fundamental plugin within the `ember-cli-deploy` ecosystem, designed to facilitate the build process of Ember CLI applications as part of a continuous deployment pipeline. Its primary role is to compile and output all necessary application assets into a specified directory. It seamlessly integrates into the `ember-cli-deploy` workflow by implementing the `configure` and `build` pipeline hooks, handling tasks traditionally performed by `ember build`. The current stable version is 3.0.0, with a release cadence often tied to updates in Ember CLI itself and its underlying dependencies. This plugin differentiates itself by providing a robust, configurable build step that is abstracted and integrated directly into the deployment process, allowing developers to define build environments and output paths within their `config/deploy.js` file, ensuring consistency across deployments without manual intervention. It is not a standalone build tool but rather an essential component for automated Ember deployments.
npm install ember-cli-deploy-buildVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install the `ember-cli-deploy-build` plugin, configure its behavior (like target environment and output path) within your `config/deploy.js` file, and then initiate a production deployment which will trigger the build process.
Ensure your project's Node.js environment meets the minimum requirements of '14.* || 16.* || 18.* || >= 20' as specified in the package's engines field. Update Node.js if necessary.
Review your deployment strategy for hidden files. If you previously relied on them being excluded, you might need to implement explicit exclusion rules in a subsequent `ember-cli-deploy` plugin (e.g., `s3`) or adjust your build output if possible.
To run tests for `ember-cli-deploy-build` itself, use `yarn test` as described in its documentation. For your application's tests, use `ember test` as usual.
Only use `EMBER_CLI_DEPLOY_REUSE_BUILD` when you are confident that your application code and build options (e.g., `environment`, `outputPath`) have not changed. Always perform a clean build for production deployments.
Ensure the `build` object in your `config/deploy.js` includes an `environment` property, e.g., `build: { environment: 'production' }`.Upgrade your Node.js installation to version 14, 16, 18, or 20, or newer, as specified by the package's `engines` field.
Verify that `ember-cli-deploy-build` is listed in your `package.json` and try running `npm install` or `yarn install` again. Ensure `ember-cli-deploy` itself is also properly installed.