Feature idea: Let package.json accept comments (JSONC support)

[d0lwl0b]

Hi Yarn team 👋,

package.json has become the control-room for everything—from scripts and workspaces to publishing metadata.
The problem? It has no room for little notes. Any time we want to leave a hint like “why this version is pinned” or “please don’t touch this field,” we’re forced to open a separate doc (that nobody reads) or add a fake field that breaks tooling.

It would be wonderful if Yarn could read the file as JSONC—plain JSON plus:

• // single-line comments
• /* block comments */
• trailing commas that don’t trip us up

Tooling such as VS Code and TypeScript already speak JSONC, and it stays valid JSON after stripping comments, so the publishing story remains safe.

Benefits at a glance:

1. Self-documenting configs – future teammates understand choices without hunting docs.
2. Cleaner PR reviews – no need for workaround fields or README edits just to explain a line.
3. Zero impact on the registry – Yarn could strip comments before packing, so nothing changes downstream.

Thanks for considering! I’d love to hear thoughts or pitfalls I might have missed.