René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"The inferred type of \"X\" cannot be named without a reference to \"Y\". This is likely not portable. A type annotation is necessary.","articleBody":"# Bug Report\r\n\r\n\u003c!--\r\n  Please fill in each section completely. Thank you!\r\n--\u003e\r\n\r\n### 🔎 Search Terms\r\n\r\n\u003c!--\r\n  What search terms did you use when trying to find an existing bug report?\r\n  List them here so people in the future can find this one more easily.\r\n--\u003e\r\n\r\ninferred type cannot be named, symlink node_modules\r\n\r\n### 🕗 Version \u0026 Regression Information\r\n\r\n\u003c!-- When did you start seeing this bug occur?\r\n\r\n\"Bugs\" that have existed in TS for a long time are very likely to be FAQs; refer to\r\n  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs\r\n\r\nIf possible, please try testing the nightly version of TS to see if it's already been fixed.\r\nFor npm: `typescript@next`\r\nThis is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly\r\n\r\nNote: The TypeScript Playground can be used to try older versions of TypeScript.\r\n\r\nPlease keep and fill in the line that best applies:\r\n--\u003e\r\nI'm verifying the problem on the `typescript@4.1.3`. I've not tried older versions but at least is also reproducible on the `@next` version as of today.\r\n\r\nIt is probably a regression or a corner case related with other issues opened and already closed like:\r\n\r\n- https://github.com/microsoft/TypeScript/issues/30858\r\n- https://github.com/microsoft/TypeScript/issues/28689\r\n- https://github.com/microsoft/TypeScript/issues/2338\r\n- https://github.com/microsoft/TypeScript/issues/29221\r\n\r\n### ⏯ Playground Link\r\n\r\n\u003c!--\r\n  A link to a TypeScript Playground \"Share\" link which shows this behavior\r\n\r\n  The TypeScript Workbench can be used for more complex setups, try\r\n  https://www.typescriptlang.org/dev/bug-workbench/\r\n\r\n  As a last resort, you can link to a repo, but these will be slower for us to investigate.\r\n--\u003e\r\n[Link for a repo where the problem is being reproduced](https://github.com/mistic/reproduce-typescript-problem-when-symlinking-node_modules)\r\n\r\n\u003e NOTE: Just clone the repo and run `yarn tsc`\r\n\r\n### 💻 Code\r\n\r\n\u003c!-- Please post the relevant code sample here as well--\u003e\r\n\r\nAll the relevant code can be found at https://github.com/mistic/reproduce-typescript-problem-when-symlinking-node_modules\r\n\r\nIt is just reproducing a similar setup that I had on other project that was generating the problem:\r\n\r\n- node_modules are a symlink to another location that is not a direct parent of the symlinked node_modules\r\n- we are using types in the compilation from a library where those types are just exported from other one, like for example `withRouter` within `react-router-dom` that is just a plain export from the same type on `react-router`.\r\n\r\n### 🙁 Actual behavior\r\n\r\nI got the following error:\r\n\r\n```\r\nerror TS2742: The inferred type of 'Nav' cannot be named without a reference to '../../deps/node_modules/@types/react-router'. This is likely not portable. A type annotation is necessary.\r\n\r\n8 export const Nav = withRouter(({ history }: NavProps) =\u003e {\r\n               ~~~\r\n\r\n\r\nFound 1 error.\r\n```\r\n### 🙂 Expected behavior\r\n\r\n\u003c!-- What you expected to happen instead, and why --\u003e\r\n\r\nI was expecting no error at all and that the typescript compiler was just able to find all the respective modules. I've tried everything that I thought was related like enabled the `preserveSymlinks`. The only thing that stops the error is importing the `withRouter` type directly from `react-router` and not from `react-router-dom` but that doesn't make very sense because I actually want to use the `react-router-dom` on a couple of places.\r\n\r\n\\cc @weswigham @sheetalkamat @andrewbranch because I saw you previously worked to try to solve similar issues. \r\n","author":{"url":"https://github.com/mistic","@type":"Person","name":"mistic"},"datePublished":"2021-02-19T00:03:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":136},"url":"https://github.com/42873/TypeScript/issues/42873"}