Upgrading type-is from 2.x to 3.x

Comparison of the public API of type-is 2.1.0 and 3.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths	0
Removed exports	1
Changed signatures	3
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	7

Removed exports

import	export	kind	Before
`type-is`	`is`	function	`(mediaType: string, types: string[]): string \| false \| (mediaType: string, ...types: string[]): string \| false`

Changed signatures

export	Before	After
`type-is · match`	`(expected: string \| false, actual: string): boolean`	`(expected: string): (actual: string) => boolean`
`type-is · hasBody`	`(request: IncomingMessage): boolean`	`(req: RequestLike): boolean`
`type-is · normalize`	`(type: string): string \| false`	`(value: string, options?: NormalizeOptions \| undefined): string \| string[]`

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

	Before	After
`engines.node`	`>= 18`	`>= 22`

New exports (7)

import	export	kind
`type-is`	`TypeIs`	class
`type-is`	`RequestLike`	interface
`type-is`	`TypeIsOptions`	interface
`type-is`	`DEFAULT_LOOKUP`	function
`type-is`	`ParameterValue`	type
`type-is`	`NormalizeOptions`	interface
`type-is`	`DEFAULT_PARAMETER_VALUE`	function

Frequently asked questions

What are the breaking changes when upgrading type-is from 2 to 3?

Between type-is 2.1.0 and 3.0.0, Vigia found 1 removed exports, 3 changed signatures and 0 removed or changed class or interface members.

What became deprecated in type-is 3?

0 exports or members are newly marked as deprecated in type-is 3.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/type-is/upgrade?from=2.1.0&to=3.0.0