Jeremy Whitlock

I ended up with a much simpler approach, although sanitizing the paths returned by `ambiguousPath` required a little extra work to figure out. All-in-all, I think PR #44 is in...

While I think we could/should do client-side validation of this, I think this may be better solved by making the Management API handle this better. Let me file a bug...

I think we were waiting on @hiteshshahjee to respond to #179 but I've bumped that PR to get what we needed. Once merged, release will happen immediately.

We will address this during the next release. But is this a deprecation, as in just a warning, or are things not working?

It's a warning, it doesn't stop you from installing/updating `apigeetool` so as mentioned [above](https://github.com/apigee/apigeetool-node/issues/184#issuecomment-612991708), we'll address this in the next release.

I understand that this is confusing but I just tested this with every version of Node.js and this is just a **WARNING** and as I mentioned [above](https://github.com/apigee/apigeetool-node/issues/184#issuecomment-625938373), not only should...

The deprecation of `request` **IS** a warning _(the output clearly states this)_, but the `EACCESS` is unrelated to this issue or the deprecation of the aforementioned module. There is no...

I think you're crossing the streams here, unless you are installing/using `apigeetool`, this isn't the proper place to report this. This issue is for the need to update the `request`...

I really wish you would read the comments before posting problems here, as the problems you're mentioning **ARE NOT** related to this project. This project has nothing to do with...

Well, `#` is the comment character and once seen it will treat everything after it as a comment. I've been trying to see if there is a way to escape...