Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include resolutions example in README #318

Merged
merged 1 commit into from
Apr 8, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ module.exports = function() {
*/
useVersionCompatibility: true,
/*
If set to true, all npm scenarios will use `yarn` for install with the `--no-lockfile` option. At cleanup, your
If set to true, all npm scenarios will use `yarn` for install with the `--no-lockfile` option. At cleanup, your
dependencies will be restored to their prior state.
*/
useYarn: true,
Expand All @@ -141,7 +141,7 @@ module.exports = function() {
}
},
/*
When writing scenarios that depend upon ember versions supplied by bower, you must explictly remove the
When writing scenarios that depend upon ember versions supplied by bower, you must explictly remove the
npm ember-source dependency if your addon defines an ember-source in its own package.json devDependencies
*/
npm: {
Expand All @@ -162,6 +162,14 @@ module.exports = function() {
npm: {
devDependencies: {
'ember-source': '2.11.0'
},
/*
When `useYarn` is true, you can optionally define yarn resolutions to enforce a
specific dependency version to be installed. This is useful if other libraries
you depend on include different versions of a package.
*/
resolutions: {
'lodash': '5.0.0'
}
}
},
Expand Down