-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge NpmIntellisense into this extension #9
Comments
I also use them together and have a problem: say I'd like to import a relative file and want to type Update The same problem exists for relative paths like |
@donaldpipowitch the solution is to unbind |
@dbettini Thank you for the hint. Didn't know that. I also added ".." as first suggestion which makes it even faster since you only have to hit enter. |
Awesome, thanks. |
@eyalellenbogen: PathIntellisense is not just for import statements but for path completion in general. You can for example also autocomplete url in html src attributes. Also in a few years, npm could be replaced by another package manager while autocompletion for paths is something I don't expect to go away soon. This is why I created two extension separately. |
Hi again,
What do you think about merging your other extension (https://github.com/ChristianKohler/NpmIntellisense) with this one?
I think it makes sense to have one extension take care of import statements.
E
The text was updated successfully, but these errors were encountered: