Vigia

Upgrading onetime from 7.x to 8.x

Comparison of the public API of onetime 7.0.0 and 8.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths0
Removed exports0
Changed signatures1
Removed class or interface members0
Changed class or interface members0
Newly deprecated0
Requirement changes (engines, peer dependencies)1
New exports1

Removed exports

None detected.

Changed signatures

exportBeforeAfter
onetime · default<ArgumentsType extends unknown[], ReturnType>(fn: (...arguments_: ArgumentsType) => ReturnType, options?: Options | undefined): (...arguments_: ArgumentsType) => ReturnType<ArgumentsType extends unknown[], ReturnType>(fn: (...arguments_: ArgumentsType) => ReturnType, options?: Options | undefined): OnetimeFunction<ArgumentsType, ReturnType>

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

BeforeAfter
engines.node>=18>=22
New exports (1)
importexportkind
onetimeOnetimeFunctiontype

Frequently asked questions

What are the breaking changes when upgrading onetime from 7 to 8?

Between onetime 7.0.0 and 8.0.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in onetime 8?

0 exports or members are newly marked as deprecated in onetime 8.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/onetime/upgrade?from=7.0.0&to=8.0.0