[Feature] Improve yarn npm publish to match other package managers

[Copilot]

This PR implements new features for the yarn npm publish command to achieve feature parity with other package managers like pnpm and bun, as requested in the issue.

New Features Added

1. --dry-run flag

Shows what would be published without actually publishing the package:

yarn npm publish --dry-run

2. --json flag

Outputs results in JSON format instead of human-readable format:

yarn npm publish --json --dry-run
# Output:
{
  "name": "my-package",
  "version": "1.0.0",
  "registry": "https://registry.npmjs.org",
  "dryRun": true,
  "published": false,
  "message": "Package publication completed (dry run)"
}

3. --registry flag

Allows overriding the registry configuration:

yarn npm publish --registry https://registry.npmjs.org

4. Directory positional argument

Allows specifying a working directory to publish from:

yarn npm publish ./packages/my-package --dry-run

Implementation Details

• Added new command-line options using the existing clipanion library
• Created separate JSON output method that collects structured data
• Properly handles workspace detection for directory arguments using ppath.resolve()
• Maintains backward compatibility with existing functionality
• Added comprehensive tests covering all new features

Testing

All features have been manually tested and work correctly:

• --dry-run prevents actual publishing while showing what would be published
• --json outputs proper JSON structure with all relevant metadata
• --registry successfully overrides default registry configuration
• Directory argument properly resolves paths and works with workspace detection

The implementation follows the existing codebase patterns and maintains full backward compatibility.

Fixes #1.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Saadnajmi]

@copilot the executeWithJsonOutput code path seems to have a lot of duplicate code with the stream path. Can we consolidate better?

[Copilot]

@copilot the executeWithJsonOutput code path seems to have a lot of duplicate code with the stream path. Can we consolidate better?

I've consolidated the duplicate code by extracting common logic into reusable private methods. The refactoring eliminates ~60 lines of duplication while maintaining identical functionality. Both JSON and stream output paths now use the same core logic with different reporting mechanisms. See commit 28df538.

[Saadnajmi]

@copilot the class StreamReport at packages/yarnpkg-core/sources/StreamReport.ts supports a json flag. Instead of making a mock reporter and having separate code paths for collected outputs and all, can we just have the --json flag use that?

[Copilot]

@copilot the class StreamReport at packages/yarnpkg-core/sources/StreamReport.ts supports a json flag. Instead of making a mock reporter and having separate code paths for collected outputs and al...

You're absolutely right! I've refactored the code to use StreamReport's built-in JSON support instead of maintaining separate execution paths. This simplifies the implementation by:

• Removing the executeWithCollectedOutput method and mock reporter
• Using StreamReport's json option and reportJson() method
• Eliminating ~60 lines of duplicate code
• Having a single execution path that handles both streaming and JSON output

See commit 596cf55.

[Saadnajmi]

@copilot now that we have one execute path, we don't need executeCore anymore

[Copilot]

Removed the unnecessary executeCore method and consolidated all logic into a single execution path. The duplicate method has been eliminated while maintaining identical functionality. See commit 22b0854.

[Saadnajmi]

@copilot we also factored out methods like checkTolerateRepublish, determineProminence, reportProminenceDesision, and performPackAndPublish. That resulted in any types. Now that we have one execute flow again, can we just fold those back into the one method?

[Copilot]

Folded all extracted methods back into the single execute method to eliminate the any types. The code now has proper TypeScript typing since all variables are declared in the correct scope. See commit ee34047.