Stuck on an issue?
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.
Imported helper support requires `"moduleResolution": "node"` in tsconfig
See original GitHub issueOtherwise typescript can’t find tslib in local node_modules. (see #12)
Running tsc without that option works, so there must be a better way of finding tslib than using require.resolve.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Documentation - Module Resolution - TypeScript
Module resolution is the process the compiler uses to figure out what an import refers to. Consider an import statement like import {...
Read more >Typescript module resolution not working - Stack Overflow
When I hover the 'utils/IntHelper' part in my import line in the typescript file VSCode would also show the correct path to that...
Read more >Typescript does not resolve modules through tsconfig.json's ...
Whenever I create a component and try to import a service like this: ... does it help? ... I have `moduleResolution: node` set...
Read more >tsconfig.json demystified (Part III) | by Alex Tzinov - Medium
This part will cover Module Resolution Options. ... TL;DR Improves the support of importing pre-ES6, CommonJS modules by injecting helper ...
Read more >Module Resolution or Import Alias: The Final Guide - Raul Melo
Also, you always need to guess how many levels you have to go up and down to import your code. Of course, modern...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Back to original bug, reading typescript documentation it seems
classicresolution is mostly for backwards compatibility anyway, so closing as won’t fix.With the master branch it does work. Could you release it ?