CodeFix to import entire module into single variable

[normalser]

Not sure if this would be possible but it would be nice if one could import entire module into single variable.

For example CodeFix on bluebird or on mapSeries

would offer import * as bluebird from 'bluebird'

[zpdDG4gta8XKpMCd]

it would require a long list of configurable aliases #13270 just like for #13084:

"codefixes": {
    "import": {
        "aliases": {
            "bluebird": "../../bluebrid.js"
        }
     }
 }

[aluanhaddad]

This comment seems relevant leebyron/ecmascript-more-export-from#11 (comment) Specifically the performance characteristics of this pattern are perhaps significant.

[ChiriVulpes]

I wonder if this could be fixed relatively easily by piggybacking on the exports from the module. For instance, in the screenshot that @normalser provided, he requests a specific property of the bluebird file. If you take off the bluebird part, and just do mapSeries, it should already offer you to import that as import { mapSeries } from "bluebird";
As a result, the codefixer could see bluebird.mapSeries, see that bluebird is undefined, but see you're trying to get something specific from it, look for that specific thing that you're getting (in this case, mapSeries), then suggest importing everything into the bluebird variable you're using. import * as bluebird from "bluebird";

[mhegazy]

This should not be needed with the auto-import feature.

[ChiriVulpes]

See the OP. The request is to import an entire module into one variable, not to import one export of a module.

[DanielRosenwasser]

We now have a refactoring to go between the two:

Not quite what you want but it's close.

[ChiriVulpes]

That'll be nice for refactoring. I think this issue is still useful for writing the code, as that code fix will be more of a workaround since it takes more steps.

I can imagine being used to using the namespace import in one file and then moving to another and starting to do it that way, but it's not imported yet. There's no code fix for that, so then you have to first import the child, then change it to a namespace import at the top of the file. I could also imagine copying code that uses the namespace style and having to do the workaround for that as well.

As a result I still think this issue is worth keeping, even if it's implemented a long way down the road.

[RyanCavanaugh]

This doesn't seem to be a common request.