Jeff An

 `npm list -g` showing nothing installed globally

  Here's the output from my laptop and a repro of the bug

also repros in my `tmp` folder, where there is no `package.json`: 

any other information I can provide here @milaninfy ? only thing that seems to definitively fix the issue for the next invocation is `npx clear-npx-cache`

friendly bump...

Some possibly related weird behavior. Here `npx` asks me if I want to install the same package version twice. And invoking `npx [email protected] -V` does not work in a folder...

Thanks for the response! A few questions: 1. Using `npm-package-arg`, these two things seem to have the same "name". What field from the `na` result is used for the cache...

OK, but that doesn't seem to explain the original issue, where running `npx package@^range` did *not* look for the latest entry against `npm`'s registry? Your comment would seem to imply...

Yes, we know it works on some people's machines and not on others'. But as you can see from earlier in this thread, I've provided logs and screenshots from multiple...

I would be totally OK with the behaviour described by @kyle-blair as well, as long as `--no-cache` truly busted the cache and always fetched the latest matching version based on...