Upgrading cookie from 1.x to 2.x
Comparison of the public API of cookie 1.1.1 and 2.0.1, 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 | 2 |
| Changed signatures | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
cookie | parse | function | (str: string, options?: ParseOptions | undefined): Cookies |
cookie | serialize | function | (cookie: SetCookie, options?: StringifyOptions | undefined): string | (name: string, val: string, options?: SerializeOptions | undefined): string |
Changed signatures
| export | Before | After |
|---|---|---|
cookie · stringifySetCookie | (cookie: SetCookie, options?: StringifyOptions | undefined): string | (name: string, val: string, options?: SerializeOptions | undefined): string | (cookie: SetCookie, options?: StringifyOptions | undefined): string |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=18 | >=22 |
Frequently asked questions
What are the breaking changes when upgrading cookie from 1 to 2?
Between cookie 1.1.1 and 2.0.1, Vigia found 2 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in cookie 2?
0 exports or members are newly marked as deprecated in cookie 2.0.1.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/cookie/upgrade?from=1.1.1&to=2.0.1