Respect Node's `--loader` for VS Code Intellisense

I would like VS Code to be able to use a custom Node.js loader for Intellisense.

For example, if I remove the .mjs extension from my code, I can no longer see the Intellisense for mime-types.mjs.

But my custom loader does not require the extension.

Here is what I am hoping to see: (without the .mjs extension on the import)

I can see the .html reference in the Intellisense drop down.

But here is what I actually see:

I think that now Node.js loaders are going through the normalization process - heading out of experimental, it is a good time for VS Code to start working on respecting loaders.

Perhaps this could live in .vscode/settings.json:

// .vscode/settings.json
{
    "loader": "./loader.mjs"
}

It would be important to provide different loaders for different directories for more complex projects/monorepos, etc:

// .vscode/settings.json
{
    "loader": {
        "./app-one": "./loaders/my-custom-loader-1.mjs",
        "./app-two": "./loaders/my-custom-loader-2.mjs",
        "./app-three": "react-loader"  // <-- Uses a package as a loader
    }
}

Iniziate esaminando la configurazione proposta del loader in .vscode/settings.json e il comportamento di Node.js --loader descritto nell’issue. Determinate come Intellisense risolve attualmente gli import senza estensione, quindi definite i criteri di completamento per usare un loader o loader diversi per directory, inclusi i loader basati su pacchetti.