fix(@angular/cli): resolve the package name inside npm workspace members

[Arthur031221]

PR Checklist

• The commit message follows our guidelines: http://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: #32787

Running ng update @angular/core from an Angular app inside an npm workspace prints Found 0 dependencies. and fails with Package '@angular/core' is not a dependency. An outdated CLI hands over to a temporary install of the latest one, so upgrading from an older version fails the same way. The issue has 23 reactions and several users report the same failure.

getCurrentPackageName parses the output of npm pkg get name. Inside a workspace member npm prints an object keyed by the workspace name ({ "app": "app" }) instead of a string. That object was used as the package name, so parseNpmLikeDependencies never found the member's dependencies.

What is the new behavior?

The command output is only used if it's a string. Otherwise the name comes from the package.json in the current directory. ng update now lists the dependencies of the workspace member.

Added specs for the name and the dependencies of a workspace member. pnpm bazel test //packages/angular/cli:test passes.

Does this PR introduce a breaking change?

• Yes
• No

Assisted by Claude/Codex.

Closes #32787

[gemini-code-assist]

Code Review

This pull request updates the PackageManager to handle cases where npm prints an object keyed by the workspace name instead of a string. If the parsed output is not a string, it falls back to reading the package.json file. Unit tests have been added to verify this behavior and to test listing dependencies of an npm workspace member. I have no feedback to provide as there are no review comments.

[alan-agius4]

Thank you for the contribution! Closing in favor of #34308, which also prioritizes reading package.json directly to avoid spawning an extra package manager subprocess and handles single-entry workspace objects from npm pkg get name.