I've been spending a bunch of time on NPM doing some research on packages dependent on gax. I've noticed that some packages that are part of google-cloud-node list the repository as google-cloud-node, without pointing to the subdirectory for that package. (example - https://www.npmjs.com/package/@google-cloud/gkemulticloud). Other packages point to archived repos, which I'm assuming is part of the monorepo migration (example - https://www.npmjs.com/package/@google-cloud/os-login) and then the archived repo helpfully points to the specific subdirectory within google-cloud-node. Given that I'm new to this space I have a few questions about all of this.

1. Do we plan to update the repos on npm of packages that end up in the monorepo to have the "repository" field reflect the change?
2. If so, for those packages in google-cloud-node, any reason why we can't utilize the "directory" field in the package.json to point to the particular path just to make it easier for users finding the repo via npm? I'd be happy to help make those updates where needed.