Skip to content

platform packages lack peerDependencies cross-link to launcher #4

Description

@younna-ai-opencode

Problem: a direct npm i @systemfsoftware/claude-code-comment-checker-linux-x64 installs a raw platform package with no relation to the launcher that resolves it; version skew between a directly-installed platform package and the launcher's pinned optionalDependencies is unresolvable at runtime and surfaces as a confusing BinaryNotFound.

Suggested fix (advisory, defer): add a peerDependencies cross-link (launcher name + version) on generated platform manifests, or document that platform packages are only installable transitively via the root package (+ add a peerDependenciesMeta warning).

Evidence: scripts/release/generate-platform-manifest.ts pkg — generated manifest carries name, os, cpu, libc, files — no peerDependencies.

Source: branch comment-checker-npm @ 23dedfd5abbbdfd35c8e883252b4055235b55654 (PR link backfilled after ship).

Metadata: Severity: P2 / Confidence: 50 / Reviewer(s): adversarial / Finding ID: generate-platform-manifest-peer-deps-crosslink

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions