This PR adds the ability to run ember dependency-lint as a standalone Ember CLI command, which is much faster when debugging a dependency conflict than re-running the tests from scratch each time. With this flow, the failing tests are the indicator that you have a problem, and the command is the tool for correcting it.
The change also moves dependency lint configuration out of ember-cli-build.js and into a dedicated config/dependency-lint.js file, which is necessary for the command to be able to read the config.
See the updated README for examples of what the output looks like.
Some end-to-end testing for the actual Command and BroccoliPlugin implementations would be nice to add at some point, but I'll probably hold off on that until whenever we open source this (likely an Engineering Time project).
This PR adds the ability to run
ember dependency-lint
as a standalone Ember CLI command, which is much faster when debugging a dependency conflict than re-running the tests from scratch each time. With this flow, the failing tests are the indicator that you have a problem, and the command is the tool for correcting it.The change also moves dependency lint configuration out of
ember-cli-build.js
and into a dedicatedconfig/dependency-lint.js
file, which is necessary for the command to be able to read the config.See the updated README for examples of what the output looks like.
Some end-to-end testing for the actual
Command
andBroccoliPlugin
implementations would be nice to add at some point, but I'll probably hold off on that until whenever we open source this (likely an Engineering Time project).Prime: @kswilster /cc @salsify/frontend-developers