[Snyk] Upgrade jwt-decode from 3.1.2 to 4.0.0

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade jwt-decode from 3.1.2 to 4.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 6 versions ahead of your current version.

• The recommended version was released on a year ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	169	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	169	Proof of Concept

Release notes

Package name: jwt-decode

• 4.0.0 - 2023-10-27
  

  A new version of the library, including a couple of improvements:

  • No longer include a polyfill for atob, as this is supported in all major browsers (and node environments > 14).
  • Compile to ES2017, dropping support for anything that does not support ES2017 (which should be very limited according to caniuse)
  • Use Node's atob when running on node.
  • Drop support for Node 14 and 16, add support for Node 20.
  • Add support for package.json's exports field, for better CJS/ESM support
  • Reorganize build artifacts for better CJS/ESM support (cjs and esm needs to be their own directory with a cjs specific package.json file)
  • Drop manual UMD bundle creation in index.standalone.ts, but rely on rollup instead.
  • Infer JwtPayload and JwtHeader default types from the header argument by using overloads.

  Even though some users might experience breaking changes, mostly because of the exports field, the majority should be able to update without making any changes, assuming the SDK is used in environments with support for atob.

  Migration to v4.0.0

  The jwtDecode function is now no longer the default export, and is instead provided as a named export. Make sure to update your code in places where you are importing this function:

  -import jwtDecodefrom "jwt-decode";
  +import { jwtDecode } from "jwt-decode";

• 4.0.0-beta.4 - 2023-09-05
  

  Breaking changes

  • Raise minimum Node.js version to 18 #209 (jonkoops)

  Fixed

  • fix default condition should be the last one #199 (frederikprijck)
• 4.0.0-beta.3 - 2023-08-16
  

  Breaking changes

  • Drop UMD bundle #193 (frederikprijck)

  Changed

  • Use modern JavaScript syntax #187 (jonkoops)
  • Use ESNext as default module system #188 (jonkoops)
  • Avoid using any bundlers but use tsc instead #192 (frederikprijck)
• 4.0.0-beta.2 - 2023-08-04
  

  Changed

  • Avoid using default exports #175 (frederikprijck)
  • Make options optional no default function parameter initializer #179 (cristobal)

  Fixed

  • Ensure types are bundled and correctly linked #174 (jonkoops)
• 4.0.0-beta.1 - 2023-07-29
  

  Fixed

  • Ensure build is run on prepack #167 (frederikprijck)
• 4.0.0-beta.0 - 2023-07-28
  

  A new version of the library, including a couple of improvements:

  • No longer include a polyfill for atob, as this is supported in all major browsers (and node environments > 14).
  • Compile to ES2017, dropping support for anything that does not support ES2017 (which should be very limited according to caniuse)
  • Use Node's atob when running on node.
  • Drop support for Node 14, add support for Node 20.
  • Add support for package.json's exports field, for better CJS/ESM support
  • Reorganize build artifacts for better CJS/ESM support (cjs and esm needs to be their own directory with a cjs specific package.json file)
  • Drop manual UMD bundle creation in index.standalone.ts, but rely on rollup instead.
  • Infer JwtPayload and JwtHeader default types from the header argument by using overloads.

  Additionally, this PR ensures the file size is decreased:

  • ESM and CJS decreased by 22%
  • UMD decreased by 37%

  Even though some users might experience breaking changes, mostly because of the exports field, the majority should be able to update without making any changes, assuming the SDK is used in environments with support for atob.

• 3.1.2 - 2020-11-16
  

  3.1.2

from jwt-decode GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Build:

• Upgrade jwt-decode dependency from version 3.1.2 to 4.0.0 in package.json.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR upgrades the jwt-decode dependency from version 3.1.2 to 4.0.0. The upgrade includes breaking changes in how the library is imported and used, along with improvements in bundle size and modern JavaScript support. The update also addresses security vulnerabilities related to ReDoS in cross-spawn and path-to-regexp dependencies.

Class diagram for jwt-decode import changes

classDiagram
    class JwtDecode {
        <<interface>>
        +decode(token: string): JwtPayload
    }
    class JwtPayload {
        +header: JwtHeader
        +payload: Object
    }
    class JwtHeader {
        +alg: String
        +typ: String
    }
    note for JwtDecode "jwtDecode is now a named export instead of a default export"

Loading

File-Level Changes

Change	Details	Files
Update jwt-decode dependency version with breaking changes	Changed import syntax from default to named export Dropped support for Node.js versions 14 and 16 Added support for Node.js 20 Removed atob polyfill in favor of native implementations Added package.json exports field for better CJS/ESM support Improved bundle size with 22% reduction for ESM/CJS and 37% for UMD	packages/artifact/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.