将 js-yaml 从 4.x 升级到 5.x

根据 TypeScript 类型自动比较 js-yaml 4.3.2 与 5.4.2 的公开 API。签名变化表示可能存在不兼容变更，并非确定结论。

概要

已删除的导入路径	0
已删除的导出	7
已修改的签名	3
已删除的类或接口成员	9
已修改的类或接口成员	3
新增弃用	2
要求变化（engines、peer 依赖）	0
新增导出	94

已删除的导出

import	export	kind	之前
`js-yaml`	`Mark`	interface	`interface`
`js-yaml`	`Type`	class	`class`
`js-yaml`	`State`	interface	`interface`
`js-yaml`	`EventType`	type	`"open" \| "close"`
`js-yaml`	`DEFAULT_SCHEMA`	variable	`Schema`
`js-yaml`	`SchemaDefinition`	interface	`interface`
`js-yaml`	`TypeConstructorOptions`	interface	`interface`

已修改的签名

export	之前	之后
`js-yaml · dump`	`(obj: any, opts?: DumpOptions \| undefined): string`	`(input: any, options?: DumpOptions \| undefined): string`
`js-yaml · load`	`(str: string, opts?: LoadOptions \| undefined): unknown`	`(input: string, options?: LoadOptions \| undefined): unknown`
`js-yaml · loadAll`	`(str: string, iterator?: null \| undefined, opts?: LoadOptions \| undefined): unknown[] \| (str: string, iterator: (doc: unknown) => void, opts?: LoadOptions \| undefined): void`	`(input: string, options?: LoadOptions \| undefined): unknown[] \| (input: string, iterator: null, options?: LoadOptions \| undefined): unknown[] \| (input: string, iterator: LoadAllIterator, options?: LoadOptions \| undefined): void`

已删除的类或接口成员

member	import	之前
`Schema.extend`	`js-yaml`	`(types: Type \| SchemaDefinition \| Type[]): Schema`
`DumpOptions.styles`	`js-yaml`	`{ [x: string]: any; } \| undefined`
`DumpOptions.replacer`	`js-yaml`	`((key: string, value: any) => any) \| undefined`
`DumpOptions.quotingType`	`js-yaml`	`"'" \| "\"" \| undefined`
`DumpOptions.condenseFlow`	`js-yaml`	`boolean \| undefined`
`DumpOptions.noCompatMode`	`js-yaml`	`boolean \| undefined`
`DumpOptions.noArrayIndent`	`js-yaml`	`boolean \| undefined`
`LoadOptions.listener`	`js-yaml`	`((this: State, eventType: EventType, state: State) => void) \| undefined`
`LoadOptions.onWarning`	`js-yaml`	`((this: null, e: YAMLException) => void) \| undefined`

已修改的类或接口成员

member	之前	之后
`Schema.constructor`	`(definition: Type \| SchemaDefinition \| Type[]): Schema`	`(tags: readonly TagDefinition[]): Schema`
`YAMLException.mark`	`Mark`	`SnippetMark \| undefined`
`YAMLException.constructor`	`(reason?: string \| undefined, mark?: Mark \| undefined): YAMLException`	`(reason: string, mark?: SnippetMark \| undefined): YAMLException`

新增弃用

export	@deprecated
`js-yaml · loadAll`	Iterator is not supported.
`js-yaml · DumpOptions.sortKeys`	Use {@link transform} to reorder mapping items.

要求变化（engines、peer 依赖）

未发现。

新增导出 (94)

import	export	kind
`js-yaml`	`Node`	type
`js-yaml`	`Event`	type
`js-yaml`	`visit`	function
`js-yaml`	`mapTag`	variable
`js-yaml`	`seqTag`	variable
`js-yaml`	`setTag`	variable
`js-yaml`	`strTag`	variable
`js-yaml`	`EventId`	type
`js-yaml`	`Visitor`	type
`js-yaml`	`jsToAst`	function
`js-yaml`	`omapTag`	variable
`js-yaml`	`present`	function
`js-yaml`	`Document`	interface
`js-yaml`	`EVENT_ID`	variable
`js-yaml`	`NodeBase`	interface
`js-yaml`	`PopEvent`	interface
`js-yaml`	`mergeTag`	variable
`js-yaml`	`pairsTag`	variable
`js-yaml`	`AliasNode`	interface
`js-yaml`	`EVENT_POP`	variable
`js-yaml`	`binaryTag`	variable
`js-yaml`	`AliasEvent`	interface
`js-yaml`	`ScalarNode`	interface
`js-yaml`	`VISIT_SKIP`	variable
`js-yaml`	`intCoreTag`	variable
`js-yaml`	`intJsonTag`	variable
`js-yaml`	`realMapTag`	variable
`js-yaml`	`DUMP_SCHEMA`	variable
`js-yaml`	`EVENT_ALIAS`	variable
`js-yaml`	`MappingNode`	interface
`js-yaml`	`ScalarEvent`	interface
`js-yaml`	`ScalarStyle`	type
`js-yaml`	`VISIT_BREAK`	variable
`js-yaml`	`boolCoreTag`	variable
`js-yaml`	`boolJsonTag`	variable
`js-yaml`	`eventsToAst`	function
`js-yaml`	`nullCoreTag`	variable
`js-yaml`	`nullJsonTag`	variable
`js-yaml`	`parseEvents`	function
`js-yaml`	`ChompingMode`	type
`js-yaml`	`EVENT_SCALAR`	variable
`js-yaml`	`MappingEvent`	interface
`js-yaml`	`NOT_RESOLVED`	variable
`js-yaml`	`SCALAR_STYLE`	variable
`js-yaml`	`ScalarLayout`	interface
`js-yaml`	`SequenceNode`	interface
`js-yaml`	`VisitContext`	interface
`js-yaml`	`floatCoreTag`	variable
`js-yaml`	`floatJsonTag`	variable
`js-yaml`	`intYaml11Tag`	variable
`js-yaml`	`legacyMapTag`	variable
`js-yaml`	`timestampTag`	variable
`js-yaml`	`CHOMPING_CLIP`	variable
`js-yaml`	`CHOMPING_KEEP`	variable
`js-yaml`	`CHOMPING_MODE`	variable
`js-yaml`	`DocumentEvent`	interface
`js-yaml`	`EVENT_MAPPING`	variable
`js-yaml`	`FromJsOptions`	interface
`js-yaml`	`ParserOptions`	interface
`js-yaml`	`SequenceEvent`	interface
`js-yaml`	`TagDefinition`	type
`js-yaml`	`YAML11_SCHEMA`	variable
`js-yaml`	`boolYaml11Tag`	variable
`js-yaml`	`nullYaml11Tag`	variable
`js-yaml`	`CHOMPING_STRIP`	variable
`js-yaml`	`EVENT_DOCUMENT`	variable
`js-yaml`	`EVENT_SEQUENCE`	variable
`js-yaml`	`floatYaml11Tag`	variable
`js-yaml`	`getScalarValue`	function
`js-yaml`	`CollectionStyle`	type
`js-yaml`	`ScalarStyleRule`	type
`js-yaml`	`defineScalarTag`	function
`js-yaml`	`COLLECTION_STYLE`	variable
`js-yaml`	`PresenterOptions`	interface
`js-yaml`	`ScalarTagOptions`	interface
`js-yaml`	`defineMappingTag`	function
`js-yaml`	`DocumentDirective`	type
`js-yaml`	`FromEventsOptions`	interface
`js-yaml`	`MappingTagOptions`	interface
`js-yaml`	`defineSequenceTag`	function
`js-yaml`	`ConstructorOptions`	interface
`js-yaml`	`SCALAR_STYLE_PLAIN`	variable
`js-yaml`	`SequenceTagOptions`	interface
`js-yaml`	`ScalarTagDefinition`	interface
`js-yaml`	`constructFromEvents`	function
`js-yaml`	`MappingTagDefinition`	interface
`js-yaml`	`COLLECTION_STYLE_FLOW`	variable
`js-yaml`	`SequenceTagDefinition`	interface
`js-yaml`	`COLLECTION_STYLE_BLOCK`	variable
`js-yaml`	`SCALAR_STYLE_FOLDED_BLOCK`	variable
`js-yaml`	`DEFAULT_SCALAR_STYLE_RULES`	variable
`js-yaml`	`SCALAR_STYLE_DOUBLE_QUOTED`	variable
`js-yaml`	`SCALAR_STYLE_LITERAL_BLOCK`	variable
`js-yaml`	`SCALAR_STYLE_SINGLE_QUOTED`	variable

常见问题

将 js-yaml 从 4 升级到 5 有哪些不兼容变更？

在 js-yaml 4.3.2 与 5.4.2 之间，Vigia 发现 7 个已删除的导出、3 个已修改的签名，以及 12 个已删除或修改的类或接口成员。

js-yaml 5 中弃用了哪些内容？

js-yaml 5.4.2 中有 2 个导出或成员新被标记为弃用。

供智能体使用

GET https://vigia.coredls.cloud/v1/packages/npm/js-yaml/upgrade?from=4.3.2&to=5.4.2