Skip to content

Rust-native package map customConditions for repo-local targets #452

Description

@jununfly

This was generated by AI during triage.

Parent

  • Roadmap plan: docs/plans/2026-06-22-rust-native-typescript-module-resolution-roadmap.md
  • Package map condition plan: docs/plans/2026-06-22-rust-native-package-map-condition-set-completion.md
  • Roadmap node: 1-4-3. condition set handling for repo-local source

What to build

Read compilerOptions.customConditions from the Rust resolved TypeScript config model and apply those configured conditions to repo-local package exports / imports condition selection. The custom conditions should participate in the shared condition helper after types, import-kind/runtime condition, and node, and before default.

This must not expand node_modules, must not add a TypeScript compiler runtime dependency, and must not claim support for package-manager-specific condition semantics beyond the configured strings.

Acceptance criteria

  • The Rust resolved config model captures compilerOptions.customConditions from direct and inherited repo-local configs.
  • Package exports repo-local resolution can select a target through a configured custom condition.
  • Package imports repo-local resolution can select a target through a configured custom condition.
  • Diagnostics/profile data includes custom conditions in the effective condition set when configured.
  • Deterministic Rust fixtures cover direct config, inherited config, and fallback to default when custom conditions do not match.
  • No node_modules graph expansion or production TypeScript compiler API dependency is introduced.

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions