Where does source-map-loader fit into TypeScript compilation with Webpack?

I'm adding TypeScript to the build process of a currently all-JavaScript web app whose build process is structured around Webpack. I've been following TypeScript's Migrating from JavaScript article, and have a question about the suggested Webpack configuration¹, copied below for your convenience:

module.exports = {
    entry: "./src/index.ts",
    output: {
        filename: "./dist/bundle.js",
    },

    // Enable sourcemaps for debugging webpack's output.
    devtool: "source-map",

    resolve: {
        // Add '.ts' and '.tsx' as resolvable extensions.
        extensions: ["", ".webpack.js", ".web.js", ".ts", ".tsx", ".js"]
    },

    module: {
        loaders: [
            // All files with a '.ts' or '.tsx' extension will be handled by 'awesome-typescript-loader'.
            { test: /\.tsx?$/, loader: "awesome-typescript-loader" }
        ],

        preLoaders: [
            // All output '.js' files will have any sourcemaps re-processed by 'source-map-loader'.
            { test: /\.js$/, loader: "source-map-loader" }
        ]
    },

    // Other options...
};

The presence of awesome-typescript-loader is of course required — we want to compile TypeScript, after all. My question is about source-map-loader, used here as a pre-loader. The article is pretty terse about its purpose, saying only:

You can use awesome-typescript-loader, a TypeScript loader, combined with source-map-loader for easier debugging.

Another article adds only a bit of extra information:

Both of these dependencies will let TypeScript and Webpack play well together. awesome-typescript-loader helps Webpack compile your TypeScript code using the TypeScript’s standard configuration file named tsconfig.json. source-map-loader uses any sourcemap outputs from TypeScript to inform webpack when generating its own sourcemaps. This will allow you to debug your final output file as if you were debugging your original TypeScript source code.

Finally, source-map-loader's own README says:

source-map-loader extracts existing source maps from all JavaScript entries. This includes both inline source maps as well as those linked via URL. All source map data is passed to webpack for processing as per a chosen source map style specified by the devtool option in webpack.config.js.

Ok. So source-map-loader ingests source maps and provides them to Webpack. My question, though, is why should it be running as a pre-loader? Based on the second quote, above, it sounds like source-map-loader is supposed to pick up sourcemap outputs from TypeScript. If it runs as a pre-loader, though, it runs before normal loaders, and I don't understand how it can use output from TypeScript.

Further, I was under the impression that Webpack doesn't deal with intermediate files — in the configuration, source-map-loader only loads .jsx? files. Doesn't that mean source-map-loader won't be invoked on the results of TypeScript compilation at all?

1: Note that this Webpack configuration uses outdated syntax, listing normal loaders in the module.loaders section, and pre-loaders in the module.preLoaders section. This doesn't affect the content of this question, and an example with current syntax is available at a similar article from the same site.