Poor webpack own typings detalization

Bug report

What is the current behavior?

Loader from webpack/declarations/WebpackOptions

export interface Loader {
	[k: string]: any;
}

Loader from @types/webpack

interface Loader extends Function {
            (this: LoaderContext, source: string | Buffer, sourceMap?: RawSourceMap): string | Buffer | void | undefined;

            /**
             * The order of chained loaders are always called from right to left.
             * But, in some cases, loaders do not care about the results of the previous loader or the resource.
             * They only care for metadata. The pitch method on the loaders is called from left to right before the loaders are called (from right to left).
             * If a loader delivers a result in the pitch method the process turns around and skips the remaining loaders,
             * continuing with the calls to the more left loaders. data can be passed between pitch and normal call.
             */
            pitch?(remainingRequest: string, precedingRequest: string, data: any): any;

            /**
             * By default, the resource file is treated as utf-8 string and passed as String to the loader.
             * By setting raw to true the loader is passed the raw Buffer.
             * Every loader is allowed to deliver its result as String or as Buffer.
             * The compiler converts them between loaders.
             */
            raw?: boolean;
        }

Quite big difference)

As I understand, own types are not so detailed, as in @types/webpack But It will be nice to have the same typings with the same detalization.

Other relevant information: webpack version: beta 15 Node.js version: 10.xxx Operating System: windows

[artem-malko]

There is a temp solution, who want to use webpack beta 15 and rich typings from @types/webpack: tsconfig.json

"compilerOptions": {
    "paths": {
      "webpack": ["./node_modules/@types/webpack/index.d.ts"],
    },
}

[alexander-akait]

Let’s close in favor https://github.com/webpack/webpack/issues/11630, we need some more types for loader(s)