Parse imported variables

[privatenumber]

I believe this is a duplicate of #100. It was resolved by providing information on exported variables, but the actual request was for imports.

In my use-case, I'd like to be able to extract the variables (a & c) from a statement like this:

import/*
long comment
*/{
		a,
		b as c
}from/*
long comment
*/'file'

Additionally, I'd like to know the ranges for where the import names start and end: { a, b as c}

[guybedford]

I'm open to adding this feature, if we can try to keep the footprint overhead down.

[jaydenseric]

For find-unused-exports, to improve performance, I recently looked at replacing @babel/core with es-module-lexer but had to give up after realising that it doesn't provide the names of things imported from other modules.

In my use-case, I'd like to be able to extract the variables (a & c) from a statement like this

For my use case, I need to get the original name of the export that is imported, so for that example, b, not the alias c.

The tool find-unused-exports globs all the project modules, scans what the export names are in all modules to build a list of possibly unused exports, then goes through all the imports in the project modules, and for each import name, eliminates the corresponding export from the possibly unused exports list. Namespace imports (e.g. import * as foo from "./bar.mjs") eliminate all the exports from the imported module from the possibly unused exports list. What's left in the possibly unused exports list at the end is reported.