"Inferred type cannot be named" error caused by adding paths
to tsconfig
#57802
Labels
Bug
A bug in TypeScript
Fix Available
A PR has been opened for this issue
Needs Investigation
This issue needs a team member to investigate its status.
Milestone
🔎 Search Terms
"inferred type cannot be named", "paths"
🕗 Version & Regression Information
package.json
imports
field #55015⏯ Playground Link
https://github.com/haines/typescript-paths-inferred-type-cannot-be-named
💻 Code
Please see the linked repo (sorry, I couldn't reduce it any further).
🙁 Actual behavior
In a multiproject build where
app
depends onlib
, settingpaths
inlib
's tsconfig breaksapp
's build with🙂 Expected behavior
Adding
paths
shouldn't break the dependent project.Additional information about the issue
Judging by the PR that I was able to bisect to, this seems like it could a bad interaction between
paths
in tsconfig.json andexports
in package.json.The text was updated successfully, but these errors were encountered: