Vigia

将 file-entry-cache 从 10.x 升级到 11.x

根据 TypeScript 类型自动比较 file-entry-cache 10.1.4 与 11.1.5 的公开 API。签名变化表示可能存在不兼容变更,并非确定结论。

概要

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

已删除的导出

未发现。

已修改的签名

export之前之后
file-entry-cache · create(cacheId: string, cacheDirectory?: string | undefined, useCheckSum?: boolean | undefined, currentWorkingDirectory?: string | undefined): FileEntryCache(cacheId: string, cacheDirectory?: string | undefined, options?: CreateOptions | undefined): FileEntryCache
file-entry-cache · createFromFile(filePath: string, useCheckSum?: boolean | undefined, currentWorkingDirectory?: string | undefined): FileEntryCache(filePath: string, options?: CreateOptions | undefined): FileEntryCache
file-entry-cache · FileDescriptorMeta{ size?: number | undefined; mtime?: number | undefined; hash?: string | undefined; data?: unknown; }{ [key: string]: unknown; size?: number | undefined; mtime?: number | undefined; hash?: string | undefined; data?: unknown; }
file-entry-cache · FileEntryCacheOptions{ currentWorkingDirectory?: string | undefined; useModifiedTime?: boolean | undefined; useCheckSum?: boolean | undefined; hashAlgorithm?: string | undefined; cache?: any; }{ useModifiedTime?: boolean | undefined; useCheckSum?: boolean | undefined; hashAlgorithm?: string | undefined; cwd?: string | undefined; restrictAccessToCwd?: boolean | undefined; useAbsolutePathAsKey?: boolean | undefined; logger?: ILogger | undefined; cache?: any; }
file-entry-cache · GetFileDescriptorOptions{ useCheckSum?: boolean | undefined; useModifiedTime?: boolean | undefined; currentWorkingDirectory?: string | undefined; }{ useCheckSum?: boolean | undefined; useModifiedTime?: boolean | undefined; }

已删除的类或接口成员

memberimport之前
FileEntryCache.renameAbsolutePathKeysfile-entry-cache(oldPath: string, newPath: string): void
FileEntryCache.currentWorkingDirectoryfile-entry-cachestring | undefined
FileEntryCache._currentWorkingDirectoryfile-entry-cacheany

已修改的类或接口成员

member之前之后
default.static create(cacheId: string, cacheDirectory?: string | undefined, useCheckSum?: boolean | undefined, currentWorkingDirectory?: string | undefined): FileEntryCache(cacheId: string, cacheDirectory?: string | undefined, options?: CreateOptions | undefined): FileEntryCache
default.static createFromFile(filePath: string, useCheckSum?: boolean | undefined, currentWorkingDirectory?: string | undefined): FileEntryCache(filePath: string, options?: CreateOptions | undefined): FileEntryCache
FileEntryCache.removeEntry(filePath: string, options?: { currentWorkingDirectory?: string | undefined; } | undefined): void(filePath: string): void
FileEntryCache.createFileKey(filePath: string, options?: { currentWorkingDirectory?: string | undefined; } | undefined): string(filePath: string): string
FileEntryCache.getAbsolutePath(filePath: string, options?: { currentWorkingDirectory?: string | undefined; } | undefined): string(filePath: string): string

新增弃用

未发现。

要求变化(engines、peer 依赖)

未发现。

新增导出 (2)
importexportkind
file-entry-cacheILoggertype
file-entry-cacheCreateOptionstype

常见问题

将 file-entry-cache 从 10 升级到 11 有哪些不兼容变更?

在 file-entry-cache 10.1.4 与 11.1.5 之间,Vigia 发现 0 个已删除的导出、5 个已修改的签名,以及 8 个已删除或修改的类或接口成员。

file-entry-cache 11 中弃用了哪些内容?

file-entry-cache 11.1.5 中有 0 个导出或成员新被标记为弃用。

供智能体使用

GET https://vigia.coredls.cloud/v1/packages/npm/file-entry-cache/upgrade?from=10.1.4&to=11.1.5