Hacker News Reader

Do you always know what the legacy behaviour will do though? Nobody stops you from solving this in a more permanent / explicit way: clone repo with too strict version bounds, change it, install from your branch.

The "--force" / legacy option can't tell a difference between "broken solution that will work for you" and "broken solution which won't".

View on HN

> The "--force" / legacy option can't tell a difference between "broken solution that will work for you" and "broken solution which won't".

But probably it doesn't have to. "--force" implies that the user wants to go on and manage the consequences of what happens. Typing it requires actively adding that flag, which is a conscious decision on the part of the user. If the user wants to check by themselves if it works or not, that could be their prerogative.

Reply on news.ycombinator.com