Fix issue with upgrade-interactive and root dependencies

[JureSotosek]

Summary

First of all, I would like to say I love this project 💪🏼
Here is my little contribution, hope you consider it 🎉

So I encountered the following problem with the upgrade-interactive --latest command.

If you are using workspaces, and you have some root dependencies and some package specific dependencies. If you run upgrade-interactive --latest in one of the package folders, you will be given a choice to upgrade dependencies not only in the current package but also all other packages and the root workspace. If you decide to upgrade a dependency from the root of the workspace, the command won't upgrade the version of the dependency in the root package.json but will leave that one the same, and add that dependency to the current package folder with the new version.

So for example, in the following project: https://github.com/juresotosek/upgrade-interactive-example, if you navigate to the packages/test folder and run upgrade-interactive --latest, and then decide to upgrade typescript, there will be a new devDependency added to the packages/test/package.json and the version of typescript in root package.json won't be changed.

Solution

It turns out that upgrade-interactive --latest looks at the location of the dependency in the workspace, and runs that Add command there. Well, if the dependency is in the root, the location will be en empty string, in that case, it should default to the root of the project while now, it defaults to the current location of where the command was executed. That's what I've changed.

Test plan

Clone the above repo see the behavior.

[JureSotosek]

Not sure what change I should make to the CHANGELOG, would love some guidance on that 👍🏼

[JureSotosek]

Did anyone get a chance to check this out?

Not sure who to ping, @arcanis maybe?