Gar

You are going to need to re-create your lockfile with the [--omit-lockfile-registry-resolved](https://docs.npmjs.com/cli/v8/using-npm/config#omit-lockfile-registry-resolved) flag

I'm having trouble following this issue. Is there a dot-separated entry in your npmrc? If so that will always cause this warning to happen. Removing it/updating it to the hyphen-separated...

It doesn't appear there's an actual bug here, npm is working as expected.

> Or why not just drop the whole infer-owner/switch-users thing in the next release? This is going to be the behavior in npm 9. Wednesday's prerelease *should* have this available...

@jpg619 this is a documentation issue, the docs need to reflect how npm 7 and up do things.

I can't reproduce this in isolation in npm 9 or 10 setup: ```sh $ npm init -y $ npm init -y -w frontend $ npm pkg set scripts.lint="echo lint" -w...

In the repo itself it seems to also work in npm 10 ```sh ~/D/n/s/r/j/jellyfin-vue (master|✔) $ npm run lint -w frontend > @jellyfin-vue/[email protected] lint > eslint . --ignore-path ../.gitignore --max-warnings=0...

`npm run` does work in other workspace contexts. There's something else going on in this repo that will need more investigation ```sh ~/D/n/s/workspaces $ npm pkg get scripts -w workspace-a...

Found it. It's the fact that you have a scoped package. `--workspace` takes a path OR a package name. You're setting it to a path which becomes incorrect when it...

This seems like a docs/education issue. `.dev` does not mean "In the devDependencies of something in the current set" it means "It is in the tree because of something in...