Interoperability with Webpack import statements

[slavafomin]

Hello!

First of all, thank you for your hard and amazing work.

The thing is, that Webpack supports more complex import statements than the standard. For example it defines "query" part of the import statements, which looks like this:

import { something } from './path/to/module?query';

The ./path/to/module is an actual filesystem path to a referenced module, however, the ?query is a query part. It allows to configure different loaders for different queries, so the same module could be treated differently in different import statements.

For example import component from './component'; would import the default symbol from the ./component module normally, however, import component from './component?raw'; could be used to load the source code of the ./component file as a string and would put it into component variable (this must be configured in Webpack config). This allows to perform very powerful operations on various files and add it to the resulting bundle. We are using it to generate documentation for example.

The problem is that TypeScript doesn't understand these "extended" import statements and shows errors during type checking. We have to either put @ts-ignore on top of such imports or to use paths configuration option to redirect the compiler to a file containing, e.g.: export default '';.

If TypeScript would support interoperability with extended Webpack import statements it would be very useful in complex projects.

By the way, besides "queries", Webpack also allows to specify loaders inline.

What do you think?

[DanielRosenwasser]

Seems related to #10988