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.
Suggestion: Better error message when unable to resolve modules
See original GitHub issueRelated to our woes with #8189, if the compilation errors gave some better hinting when it was unable to resolve a module, we might not have taken so long to find the solution (and we wouldn’t have filed an issue!).
The idea would be that if there is a compilation error of cannot file module "whatever", to make some intelligent checks against the parameters the compilation is running under and suggest using --moduleResolution node if the user is not already doing so.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:9 (4 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
Happy to PR
"Cannot find module '{0}'. If you're trying to import from node_modules you probably want '--moduleResolution node'"if that’s deemed acceptable.A more complex version that checks “would this work if they had indeed used moduleResolution=node” would be ideal, but looking at the source IMO it would be needless complex considering a generic description like above is prolly satisfactory.
@mhegazy wow totally missed that doc page. It doesn’t come up on the first page of google, so not sure what (if anything) you could do to help the docs have a better SEO rank. The SO question with a link would hopefully help, as you described. Thank you.