Skip to content

TS/JS: workspace siblings importing each other by package name are not resolved (follow-on to #3789) #4254

Description

@squid-protocol

Problem

In a monorepo, import {x} from "@scope/other" where @scope/other is a sibling workspace package (package.json workspaces) is not resolved to that package's files. #3789 covers a package importing itself by name; the sibling case is the same mechanism across packages. No workspace handling exists in gitgalaxy/core on origin/main (grep).

Evidence

Found during #3789 work.

Acceptance criteria

  • Workspace package names map to their roots (package.json name + main/exports)
  • Sibling imports produce import edges
  • Fixture with two workspace packages

Out of scope

Self-reference (#3789); non-JS workspaces.

Found during: follow-on to #3789

🤖 Generated with Claude Code

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    core-engineModifications to the central physics and parsing engineenhancementNew feature, sensor, or structural signaturepriority: lowUI tweaks, documentation, and minor optimizations

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions