René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"\"Inferred type cannot be named\" error caused by adding `paths` to tsconfig","articleBody":"### 🔎 Search Terms\n\n\"inferred type cannot be named\", \"paths\"\n\n### 🕗 Version \u0026 Regression Information\n\n- This changed in PR #55015\r\n\n\n### ⏯ Playground Link\n\nhttps://github.com/haines/typescript-paths-inferred-type-cannot-be-named\n\n### 💻 Code\n\nPlease see the linked repo (sorry, I couldn't reduce it any further).\n\n### 🙁 Actual behavior\n\nIn a multiproject build where `app` depends on `lib`, setting `paths` in `lib`'s tsconfig breaks `app`'s build with\r\n\r\n```\r\nerror TS2742: The inferred type of '...' cannot be named without a reference to '...'. This is likely not portable. A type annotation is necessary.\r\n```\n\n### 🙂 Expected behavior\n\nAdding `paths` shouldn't break the dependent project.\n\n### Additional information about the issue\n\nJudging by the PR that I was able to bisect to, this seems like it could a bad interaction between `paths` in tsconfig.json and `exports` in package.json.","author":{"url":"https://github.com/haines","@type":"Person","name":"haines"},"datePublished":"2024-03-16T01:53:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/57802/TypeScript/issues/57802"}