[5.3.2] .d.ts references dom Request/Response about webpack-dev-middleware

[AviVahl]

@alexander-akait I believe this is a regression from these changes: https://github.com/webpack/webpack-dev-middleware/pull/1260/files#diff-093ad82a25aee498b11febf1cdcb6546e4d223ffcb49ed69cc275ac27ce0ccce

[luoguoxiong]

I have the same problem~

[nuintun]

+1

webpack-dev-middleware/types/index.d.ts

Lines 175 to 178 in f88067d

	type API<
	Request_1 extends import("http").IncomingMessage,
	Response_1 extends ServerResponse
	> = Middleware<Request, Response> & AdditionalMethods<Request, Response>;

Request_1 and Response_1 generic definition is unused.

[alexander-akait]

@AviVahl Weird, we don't touch ts files, just update deps, maybe regression in ts?

[alexander-akait]

Found ts regression, when you have:

/**
 * @template {IncomingMessage} Request
 * @template {ServerResponse} Response
 * @typedef {Object} Options
 * @property {{[key: string]: string}} [mimeTypes]
 * @property {boolean | ((targetPath: string) => boolean)} [writeToDisk]
 * @property {string} [methods]
 * @property {Headers<Request, Response>} [headers]
 * @property {NonNullable<Configuration["output"]>["publicPath"]} [publicPath]
 * @property {Configuration["stats"]} [stats]
 * @property {boolean} [serverSideRender]
 * @property {OutputFileSystem} [outputFileSystem]
 * @property {boolean | string} [index]
 */

ts 4.6 consider Request and Response as global classes in dom.lib.ts (as @AviVahl mention), not as local generics, very weird, let's downdgrade and fix types and report