Avoid nil package.json crash when resolving peer dependencies

[Copilot]

Module resolution could panic when peerDependencies package ID calculation received a cached package.json entry with nil contents.

• Resolver

  • Check InfoCacheEntry.Exists() before reading a peer package’s Contents.
  • Treat nil-content peer package entries the same as missing peer package metadata.

• Regression coverage

  • Added a deterministic resolver race test that reproduces a nil-content peer package.json cache entry during peer dependency resolution.

peerPackageJson := r.getPackageJsonInfo(nodeModules + name)
if peerPackageJson.Exists() {
    version := peerPackageJson.Contents.Version.Value
    // include peer version in package ID
}

[Copilot]

Pull request overview

Fixes a potential panic in the module resolver when computing a package ID with peerDependencies, where the peer’s cached package.json cache entry can be present but have nil Contents. The change ensures the resolver only reads peer package.json fields when the cache entry actually has parsed contents, and adds a deterministic concurrent regression test that reproduces the stale nil-contents cache entry scenario.

Changes:

• Guard peer dependency package ID calculation with InfoCacheEntry.Exists() to avoid dereferencing nil Contents.
• Add a deterministic race regression test that forces the nil-contents cache entry case during peer dependency resolution.

Show a summary per file

File	Description
internal/module/resolver.go	Uses InfoCacheEntry.Exists() before reading peer package.json contents while computing peer-dependent package IDs.
internal/module/resolver_test.go	Adds a deterministic concurrent regression test for the nil-contents peer package.json cache entry scenario.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Low