Vigia

将 p-queue 从 9.x 升级到 10.x

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

概要

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

已删除的导出

未发现。

已修改的签名

export之前之后
p-queue · Queue{ size: number; filter: (options: Readonly<Partial<Options>>) => Element[]; dequeue: () => Element | undefined; enqueue: (run: Element, options?: Partial<Options> | undefined) => void; setPriority: (id: string, priority: number) => void; remove?: ((id: string) => void) | undefined; }{ size: number; filter: (options: Readonly<Partial<Options>>) => Element[]; dequeue: () => Element | undefined; enqueue: (run: Element, options?: Partial<Options> | undefined) => void; setPriority: (id: string, priority: number) => void; remove: (id: string) => void; }
p-queue · Options{ readonly concurrency?: number | undefined; readonly autoStart?: boolean | undefined; readonly queueClass?: (new () => QueueType) | undefined; readonly intervalCap?: number | undefined; readonly interval?: number | undefined; readonly carryoverIntervalCount?: boolean | undefined; readonly carryoverConcurrencyCount?: boolean | undefined; readonly strict?: boolean | undefined; } & TimeoutOptions{ readonly concurrency?: number | undefined; readonly autoStart?: boolean | undefined; readonly queueClass?: (new () => QueueType) | undefined; readonly intervalCap?: number | undefined; readonly interval?: number | undefined; readonly carryoverIntervalCount?: boolean | undefined; readonly strict?: boolean | undefined; } & TimeoutOptions
p-queue · TimeoutErroranyclass
p-queue · QueueAddOptions{ readonly priority?: number | undefined; id?: string | undefined; } & TaskOptions & TimeoutOptions{ readonly priority?: number | undefined; id?: string | undefined; timeout?: number | undefined; } & TaskOptions

已删除的类或接口成员

未发现。

已修改的类或接口成员

member之前之后
default.add<TaskResultType>(function_: Task<TaskResultType>, options?: Partial<EnqueueOptionsType> | undefined): Promise<TaskResultType><TaskResultType>(function_: Task<TaskResultType>, options?: Partial<EnqueueOptionsType> | undefined): Promise<Awaited<TaskResultType>>
default.addAll<TaskResultsType>(functions: readonly Task<TaskResultsType>[], options?: Partial<EnqueueOptionsType> | undefined): Promise<TaskResultsType[]><const Tasks extends ReadonlyArray<Task<unknown>>>(functions: Tasks, options?: Partial<EnqueueOptionsType> | undefined): Promise<TaskResults<Tasks>> | <TaskResultsType>(functions: readonly Task<TaskResultsType>[], options?: Partial<EnqueueOptionsType> | undefined): Promise<Awaited<TaskResultsType>[]…
default.runningTasksreadonly { readonly id?: string | undefined; readonly priority: number; readonly startTime: number; readonly timeout?: number | undefined; readonly timeoutRemaining?: number | undefined; }[]readonly { readonly id: string; readonly priority: number; readonly startTime: number; readonly timeout: number | undefined; readonly timeoutRemaining: number | undefined; }[]

新增弃用

未发现。

要求变化(engines、peer 依赖)

之前之后
engines.node>=20—
新增导出 (2)
importexportkind
p-queueRunFunctiontype
p-queueTaskOptionstype

把这些数据交给你的 AI 智能体

Vigia 是免费的 MCP 服务器:你的编程智能体在写代码之前就能检查版本、不兼容变更和安全漏洞。无需注册,无需 API 密钥。

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

添加到 Cursor添加到 VS Code★ 在 GitHub 上加星

任何其他 MCP 客户端
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

智能体技能(SKILL.md):告诉智能体何时使用 Vigia · 用于拉取请求的 GitHub Action

常见问题

将 p-queue 从 9 升级到 10 有哪些不兼容变更?

在 p-queue 9.3.5 与 10.0.0 之间,Vigia 发现 0 个已删除的导出、4 个已修改的签名,以及 3 个已删除或修改的类或接口成员。

p-queue 10 中弃用了哪些内容?

p-queue 10.0.0 中有 0 个导出或成员新被标记为弃用。

供智能体使用

GET https://vigia.coredls.cloud/v1/packages/npm/p-queue/upgrade?from=9.3.5&to=10.0.0