Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

ember-cli-deploy-build

ember-cli-deploy128.5kMIT3.0.0

A Build Plugin for ember-cli-deploy

ember-addon, ember-cli-deploy-plugin

readme

ember-cli-deploy-build

An ember-cli-deploy plugin to build your ember-cli application

This plugin will build your ember-cli application files and output them to a directory.

What is an ember-cli-deploy plugin?

A plugin is an addon that can be executed as a part of the ember-cli-deploy pipeline. A plugin will implement one or more of the ember-cli-deploy's pipeline hooks.

For more information on what plugins are and how they work, please refer to the Plugin Documentation.

Quick Start

  • Install this plugin
$ ember install ember-cli-deploy-build
  • Run the pipeline
$ ember deploy

Installation

Run the following command in your terminal:

ember install ember-cli-deploy-build

ember-cli-deploy Hooks Implemented

For detailed information on what plugin hooks are and how they work, please refer to the Plugin Documentation.

  • configure
  • build

Configuration Options

For detailed information on how configuration of plugins works, please refer to the Plugin Documentation.

environment

The environment for which you'd like to build. This relates directly to the environments in your config/environment.js file.

Default: 'production'

outputPath

The path to the directory you'd like the project to be built in to.

Default: tmp/deploy-dist

Prerequisites

None

Tests

  • yarn test

Faster iteration while authoring deploy plugins & configs

When you're working on a deploy plugin or tweaking your deploy config, you often run ember deploy repeatedly, and each run usually invokes this plugin to do a full rebuild of your app, even though your app has not changed and the build options are identical.

You can instead reuse the build from the previous ember deploy by setting the environment variable EMBER_CLI_DEPLOY_REUSE_BUILD. This may make your interactive testing much faster. It's safe to use during development as long as you aren't actively changing your app or altering this module's environment or outputPath.

Why ember test doesn't work

Since this is a node-only ember-cli addon, we use mocha for testing and this package does not include many files and devDependencies which are part of ember-cli's typical ember test processes.

changelog

Change Log

v3.0.0 (2023-06-04)

:boom: Breaking Change

  • #88 [BREAKING] Update dependencies including required node versions (@lukemelia)
  • #76 [Breaking] Switch to Github Actions for CI (@jrjohnson)

Committers: 2

2.0.0 (2019-09-03)

Full Changelog

Merged pull requests:

  • [BREAKING] include hidden files in distFiles #55 (lukemelia)

v1.1.2 (2019-09-03)

Full Changelog

Merged pull requests:

v1.1.1 (2017-10-11)

Full Changelog

Merged pull requests:

v1.1.0 (2017-05-04)

Full Changelog

Merged pull requests:

  • Option to reuse build output during plugin development #38 (ef4)

v1.0.0 (2017-04-06)

Full Changelog

v1.0.0-beta.0 (2017-03-25)

Full Changelog

Merged pull requests:

v0.1.1 (2016-02-07)

Full Changelog

Merged pull requests:

v0.1.0 (2015-10-25)

Full Changelog

Merged pull requests:

v0.1.0-beta.1 (2015-08-08)

Merged pull requests:

  • Update README for 0.5.0 #16 (achambers)
  • use path.sep instead of / for cross-platform compatibility #15 (duizendnegen)
  • Ensure we are using the Builder from the project's version of ember-cli #14 (lukemelia)
  • Plugin base class restructure #12 (lukemelia)
  • Implement configure hook for config validation instead of willDeploy #11 (achambers)
  • A few tweaks to log output #10 (lukemelia)
  • Allow outputPath to be configurable #9 (lukemelia)
  • Add test coverage and willDeploy config validation #8 (lukemelia)
  • Now the context.distFiles prop doesn't contain the dist dir #7 (achambers)
  • Now we don't make a distinction between index and assets #6 (achambers)
  • Updated to be in line with how ember-cli-deploy handles context data #4 (achambers)
  • Add the index and assets paths to the data object #3 (achambers)
  • Add circle.yml #2 (achambers)
  • Update chalk to be a production dependency instead of dev #1 (achambers)

* This Change Log was automatically generated by github_changelog_generator