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

Support Detection of Ember/Glimmer apps as dependencies #524

Merged
merged 2 commits into from
Mar 11, 2019
Merged

Support Detection of Ember/Glimmer apps as dependencies #524

merged 2 commits into from
Mar 11, 2019

Conversation

elwayman02
Copy link
Contributor

This change allows ember-cli/glimmer to be specified as either a dependency
or devDependency of the project being updated. Currently, ember-cli-update
throws an error in some instances, since it is only checking devDependencies.

This change allows ember-cli/glimmer to be specified as either a dependency
or devDependency of the project being updated. Currently, `ember-cli-update`
throws an error in some instances, since it is only checking devDependencies.
@@ -10,14 +11,16 @@ module.exports = function getProjectOptions({
return ['addon'];
}

if (devDependencies) {
let isGlimmer = devDependencies['@glimmer/blueprint'];
if (dependencies || devDependencies) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the Object.assign eliminated the need for this conditional.

Copy link
Member

@kellyselden kellyselden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One tweak then good to merge!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants