Update dependency js-cookie to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
js-cookie	^2.1.4 -> ^3.0.0

---

Release Notes

js-cookie/js-cookie

v3.0.1

Compare Source

• Make package.json accessible in export - #​727

v3.0.0

Compare Source

• Removed defaults in favor of a builder: now to supply an api instance with particular predefined (cookie) attributes there's Cookies.withAttributes(), e.g.:

const api = Cookies.withAttributes({
  path: '/',
  secure: true
})
api.set('key', 'value') // writes cookie with path: '/' and secure: true...

• The attributes that an api instance is configured with are exposed as attributes property; it's an immutable object and unlike defaults cannot be changed to configure the api.
• The mechanism to fall back to the standard, internal converter by returning a falsy value in a custom read converter has been removed. Instead the default converters are now exposed as Cookies.converter, which allows for implementing self-contained custom converters providing the same behavior:

const customReadConverter = (value, name) => {
  if (name === 'special') {
    return unescape(value)
  }
  return Cookies.converter.read(value)
}

• withConverter() no longer accepts a function as argument to be turned into a read converter. It is now required to always pass an object with the explicit type(s) of converter(s):

const api = Cookies.withConverter({
  read: (value, name) => unescape(value)
})

• The converter(s) that an api instance is configured with are exposed as converter property; it's an immutable object and cannot be changed to configure the api.
• Started providing library as ES module, in addition to UMD module. The module field in package.json points to an ES module variant of the library.
• Started using browser field instead of main in package.json (for the UMD variant of the library).
• Dropped support for IE < 10.
• Removed built-in JSON support, i.e. getJSON() and automatic stringifying in set(): use Cookies.set('foo', JSON.stringify({ ... })) and JSON.parse(Cookies.get('foo')) instead.
• Removed support for Bower.
• Added minified versions to package - #​501
• Improved support for url encoded cookie values (support case insensitive encoding) - #​466, #​530
• Expose default path via API - #​541
• Handle falsy arguments passed to getters - #​399
• No longer support Node < 12 when building (LTS versions only)

v2.2.1

Compare Source

• #​400: Prevent XSS in the cookie attributes
• #​350: Document npm package manager usage

v2.2.0

Compare Source

• https://github.com/js-cookie/js-cookie/pull/221: Only include files in src/ when building the npm package.
• https://github.com/js-cookie/js-cookie/pull/293: Allow undocumented attributes to be passed when creating a cookie
• https://github.com/js-cookie/js-cookie/issues/276#issuecomment-268697509: Support for SameSite cookie (Strict vs Lax)
• https://github.com/js-cookie/js-cookie/pull/371: Add jsDelivr CDN to the README (Update is supported by jsDelivr and the community)
• https://github.com/js-cookie/js-cookie/issues/363: getJSON() does not work on cookie with escaped quotes

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[chawes13]

Resolved by #111

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.