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

Do not store resolutions with force-latest when --dont-save-resolutions is used #2345

Closed
wants to merge 1 commit into from
Closed

Do not store resolutions with force-latest when --dont-save-resolutions is used #2345

wants to merge 1 commit into from

Conversation

himdel
Copy link

@himdel himdel commented Aug 18, 2016

Closes #2344

Without this, there's no way to prevent --force-latest from modifying bower.json when it resolves a conflict.
This adds a --dont-save-resolutions to prevent that.

Not sure this is the best way, but it's the compatible way :).

Also, I have no idea how to get at the parsed options in Manager, directly looking at cooked argv (this._config.argv.cooked) is probably not the correct way..

Thoughts anyone? :)

…ns is used

Closes #2344

Without this, there's no way to prevent --force-latest from modifying bower.json when it resolves a conflict.
This adds a --dont-save-resolutions to prevent that.

Not sure this is the best way, but it's the compatible way :).

Also, I have no idea how to get at the parsed options in Manager, directly looking at cooked argv is probably not the correct way..
@sheerun
Copy link
Contributor

sheerun commented Mar 28, 2018

I'm posting alternative solution that updates package.json only if --save is used: #2508

@sheerun sheerun closed this Mar 28, 2018
@himdel himdel deleted the fix-resolve-save branch April 3, 2018 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

install with force-latest should not update bower.json
2 participants