`volo update localName` does not behave as expected

[ewinslow]

If I have already installed a package under a particular local name, I expect volo to use the existing configuration I've already set up, but instead it goes and does its standard github search for the right repo.

[jrburke]

Ah, I believe it is just not checking the package.json first to see where it got it from first. Looks like volo add symlink:path/to/dep also has a similar issue.