Skip to content
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

module analysis only works for relative imports #47

Open
michaelangeloio opened this issue Nov 10, 2023 · 2 comments
Open

module analysis only works for relative imports #47

michaelangeloio opened this issue Nov 10, 2023 · 2 comments
Labels
enhancement New feature or request limitation

Comments

@michaelangeloio
Copy link
Owner

Currently, we are only resolving relative imports:

fn get_relative_imports(import_sources: Vec<String>) -> Vec<String> {

It would be nice to perform the same analysis in Typescript alias paths. I am not sure about node_modules, but I am open to ideas.

@michaelangeloio michaelangeloio added enhancement New feature or request limitation labels Nov 10, 2023
@boian-ivanov
Copy link

This would be godsend, as most of the projects I work with are using aliases, so even if they're not read from the tsconfig.json, but manually added it would be a huge boost of understanding if an imported method throws 🎉

@djolejov
Copy link

Yes! I second this, aliases are always used in projects I work with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request limitation
Projects
None yet
Development

No branches or pull requests

3 participants