cookie

2.0.1 · 30 Jun 2026MIT314.8M / weekRepository Homepage npm Atom feed

Upgrading cookie From 0.1.5 to 0.2.0

Same major only

1 release in betweenevery note read

Other targets from 0.1.5Newest 0.x0.7.2 Clears its advisory0.7.0 Latest2.0.1

0.1.5yours
0.2.0target

0
changes to make: 0
advisories fixed: 2
new: 0
fixes

Security

1 advisory still affects 0.2.0

cookie accepts cookie name, path, and domain with out of bounds characterslow · GHSA-pxg6-pf52-xh8x

Upgrading to 0.7.0 clears it.

Release by release

0.2.0
14 Aug 20152 new
- new
  Add firstPartyOnly option
- new
  Hoist regular expression

1 other line we could not sort, mostly version bumps

Throw better error for invalid argument to parse
0.2.0

Upgrade to 0.2.0

npm install cookie@0.2.0

What 0.2.0 needs

Reading 0.2.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 0.2.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
1 advisory still affects 0.2.0.