Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
tsconfig's compilerOptions' paths setting ignored
See original GitHub issueTypeScript allows to modify module resolution using the paths configuration option on the compilerOptions object. The mechanics of this are described in https://www.typescriptlang.org/docs/handbook/module-resolution.html. This feature is necessary for avoiding the relative path hell by aliasing the root of the current project, and importing files relative to that root.
Currently imports that contain an alias from the paths configuration are reported with the “Cannot find module” error, even though tsc resolves them correctly.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:17
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 for this issue.
Has anyone ever gotten this to work? I define paths and if I use them e.g. in triple slash directives and hover over them, however, I get: Cannot find type definition file for ‘@yadayada/test’. So it seems the @yadayada is not even resolved in the first place…?