module analysis only works for relative imports

Currently, we are only resolving relative imports:

does-it-throw/crates/does-it-throw-wasm/src/lib.rs

Line 136 in 99fda18

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.

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 🎉

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

Navigation Menu

Repository navigation

module analysis only works for relative imports #47

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

module analysis only works for relative imports #47

Description

Activity

boian-ivanov commented on Jan 2, 2024

djolejov commented on Feb 21, 2024

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions