Zoltan Kochan

Are the GitHub registry docs suggesting to use the registry setting?

That is bad. An edit should be suggested

@statianzo `@pnpm/config` is normalizing the registry URLs and it is adding a trailing slash to them: https://github.com/pnpm/pnpm/blob/main/packages/config/src/getScopeRegistries.ts

I am not sure why you all try to include the owner in the registry URL. [The docs](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry) suggest to use: ``` @OWNER:registry=https://npm.pkg.github.com ``` Though this seems to work with...

Try pnpm v6.23.2

Well, I am not sure why it doesn't help as I tested it locally. But seems like it is a breaking change for some: https://github.com/pnpm/pnpm/issues/4052 if this doesn't help, maybe...

Maybe the issue was in this regression: https://github.com/pnpm/pnpm/issues/4052 Try pnpm v6.23.7-202112041634

We only use aliases that are used by npm cli. There no such alias in npm https://docs.npmjs.com/cli/v8/commands/npm-outdated

You can try to install pnpm using the standalone script https://pnpm.io/installation ``` curl -fsSL https://get.pnpm.io/install.sh | sh - ```

Does the standalone script work? ``` curl -fsSL https://get.pnpm.io/install.sh | sh - ``` You should restart the terminal after running it.