Upgrading p-retry from 8.x to 9.x
Comparison of the public API of p-retry 8.0.1 and 9.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 | 0 |
| Changed signatures | 2 |
| Removed class or interface members | 0 |
| Changed class or interface members | 1 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
| export | Before | After |
|---|---|---|
p-retry · Options | { readonly onFailedAttempt?: ((context: RetryContext) => void | Promise<void>) | undefined; readonly shouldRetry?: ((context: RetryContext) => boolean | Promise<boolean>) | undefined; readonly shouldConsumeRetry?: ((context: RetryContext) => boolean | Promise<boolean>) | undefined; readonly retries?: number | undefined; readonly factor?: number | undefined; readonly minTimeout?: number | undefined; readonly maxTimeout?: number | undefined; readonly randomize?: boolean | undefined; readonly maxRetryTime?: number | undefined; readonly signal?: AbortSignal | undefined; readonly unref?: boolean | … | { readonly onFailedAttempt?: ((context: RetryContext) => void | Promise<void>) | undefined; readonly shouldRetry?: ((context: RetryContext) => boolean | Promise<boolean>) | undefined; readonly shouldConsumeRetry?: ((context: RetryContext) => boolean | void | Promise<boolean | void>) | undefined; readonly retries?: number | undefined; readonly factor?: number | undefined; readonly minTimeout?: number | undefined; readonly maxTimeout?: number | undefined; readonly randomize?: boolean | undefined; readonly maxRetryTime?: number | undefined; readonly signal?: AbortSignal | undefined; readonly unre… |
p-retry · makeRetriable | <Arguments extends readonly unknown[], Result>(function_: (...arguments_: Arguments) => Result | PromiseLike<Result>, options?: Options | undefined): (...arguments_: Arguments) => Promise<Result> | <Arguments extends readonly unknown[], Result, This = unknown>(function_: (this: This, ...arguments_: Arguments) => Result | PromiseLike<Result>, options?: Options | undefined): (this: This, ...arguments_: Arguments) => Promise<Result> |
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
AbortError.constructor | (message: string | Error): AbortError | (message?: string | Error | undefined): AbortError |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading p-retry from 8 to 9?
Between p-retry 8.0.1 and 9.0.0, Vigia found 0 removed exports, 2 changed signatures and 1 removed or changed class or interface members.
What became deprecated in p-retry 9?
0 exports or members are newly marked as deprecated in p-retry 9.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/p-retry/upgrade?from=8.0.1&to=9.0.0