fix(mcp): resolve named engines using export conditions
BL
3h ago+188+188+012345678901234567890123456789-33-33-01234567890123456789
What and why
- Resolve MCP engine packages using
exsolvewith ESM import conditions, matching how the modules are loaded. - Preserve the existing package lookup order and add regression tests.
Issue
Fixes #1758
Verified
Ran it locally: yes
- Published
e2e@0.23.1: the standalone reproduction confirms the wrong export is selected. - Fix branch: pnpm build and pnpm plugins:check passed. MCP regression tests and e2e package tests passed.
Checklist
- Changeset added (
pnpm changeset) for any change to a published package, or the change is testbed, docs, or CI only. - Breaking change: title carries
!, the changeset body names what breaks and what replaces it, and the deprecation warning landed a window earlier (stability policy in CONTRIBUTING.md). - Docs updated in the same PR: the
docs/**/*.mdxpage for the behavior, andskills/e2e/if the skill describes it. - Contract change: emitted
.d.tsreviewed,tests/types/sdk-types.tsupdated; wire change edits the schema and both fixtures. - Engine contract change (
e2e/engine): changesets fore2e,@e2e-dev/web, and@e2e-dev/mobile.