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.
Make automatic adding missing imports smarter
See original GitHub issueScenario 1: Fuzzy Logic
I have a several files containing import {connect} from "react-redux";. If I use the add missing imports context menu to add the missing import for connect, the system should realize “react-redux” is far more probable module than “net”, “tls”, and “http2”, which are all recommended higher than “react-redux”, but none of which are used anywhere in my project.
Scenario 2: Respect node conventions
If I have a file ./myfolder/index.ts, I can import the file with import "./myfolder". The system currently resolves missing imports from ./myfolder as ./myfolder/index.ts, when it should actually use ./myfolder.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (3 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
@minestarks Scenario 1 sounds like it could fall under IntelliCode
Scenario two sounds like #29835, likely a configuration issue. @chriskuech Please share your tsconfig
Sorry, I don’t know off the top of my head - might well be arbitrary at the moment. @mjbvz Scenario 1 seems more in the domain of TS itself rather than IntelliCode as it could be implemented pretty deterministically without machine learning.