ember-cli-deploy-display-revisions is an Ember CLI Deploy plugin designed to list and display deployed revisions for Ember applications. Its current stable version is 3.0.0. This plugin integrates directly with the ember-cli-deploy ecosystem, providing a CLI command (`ember deploy:list`) to show recent deployments. It allows configuration of the number of revisions to display and expects revision data to be provided by other index plugins (e.g., fetchRevisions) in a specific JSON format, including details like `revision`, `version`, `timestamp`, `deployer`, and `active` status. The plugin is primarily a Node.js-only addon, meaning it does not participate in typical Ember application build or test processes, distinguishing it from front-end focused Ember addons. Release cadence is driven by updates to core dependencies like Node.js and ember-cli-deploy itself.
npm install ember-cli-deploy-display-revisionsVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install the plugin and use its primary CLI commands to list deployed revisions, including an example of specifying the number of revisions to display.
Ensure your project's Node.js environment meets the new requirements (Node.js v14, v16, v18, or v20+). Update your Node.js version if necessary. You may also need to update `ember-cli` and `ember-cli-deploy` to compatible versions.
Upgrade your Node.js environment to version 10 or higher. Review your `package.json` for `ember-cli` and `ember-cli-deploy` versions and update them if they are incompatible with Node 10+.
This is expected behavior. The plugin's functionality is exposed via `ember deploy:*` commands and its internal tests are run via `yarn test` in its own repository, not within your application context. Do not try to include this plugin in your Ember application's `app` or `tests` directories in a way that would trigger Ember CLI's build or test lifecycles.
Ensure that the `timestamp` field in the `context.revisions` data provided by your `fetchRevisions` plugin is either a millisecond timestamp (e.g., `1438232435000`) or a valid ISO 8601 string to be correctly parsed by Luxon.
Update your Node.js environment to a compatible version (14.*, 16.*, 18.*, or >= 20).
Ensure `ember-cli-deploy` is correctly installed in your project and configured. Verify that `ember deploy --help` works, indicating the `deploy` command is available.
Verify that your `fetchRevisions` plugin provides timestamps in the `context.revisions` array as either milliseconds since epoch or a valid ISO 8601 string, as expected by Luxon. For example: `{ revision: 'abc', timestamp: 1438232435000 }` or `{ revision: 'abc', timestamp: '2015-07-30T10:00:00.000Z' }`.