I’m catching up on Mirage issues, and am working on this issue requesting that we bump Faker.js to 4.0.
Mirage includes faker.js as a dependency. The idea was to provide it for a nice out-of-the-box testing experience.
Since faker is used directly by Mirage users, they have at times requested (with good reason) more control over the version. That is, faker is not really an implementation detail of Mirage, it’s more of a first-class thing.
Because of this, should I use
this.addAddonToProject in a blueprint and move it to
devDependencies? Does that mean I need to create a shim (similar to ember-cli-moment-shim)?
In general, what’s the best practice for addons wanting to make other packages available to their users?