pnpm add <pkg> throws a lot of warnings - already in devDependencies, was not moved to dependencies.

[vladorbulescu]

I can't find anything about this anywhere and it's really intriguing me. What could cause this and what does it mean? Why would pnpm go through all dependencies and report all those warnings when adding a new package?

I'm using pnpm 10.2.1 with a Nx Angular Monorepo. No workspaces.

[vladorbulescu]

I created a a package.json in an empty folder to test this out. Here is what happened:

• pnpm add <pkg> without having any devDependencies does not yield any warnings
• pnpm add -D <pkg> does not yield any warnings
• pnpm add <pkg> yields the warning as soon as you have a devDependency

This behavior is consistent in 10.2.1 and it looks like it doesn't have anything to do with any other configurations (e.g. Nx Monorepo).

[vladorbulescu]

I downgraded to 9.15.5 and the issue went away. I'll keept at it for now.

[vladorbulescu]

I was wrong. The issue doesn't happen on minimal configurations with 9.15.5, but once I did it in my Nx Monorepo it started to throw the warnings again.

[vladorbulescu]

Opened an issue.