chore(deps): update dependency http-status-codes to v2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
http-status-codes	dependencies	major	^1.3.0 -> ^2.0.0

---

Release Notes

prettymuchbryce/http-status-codes (http-status-codes)

v2.3.0: http-status-codes 2.3.0

Compare Source

• Adds 103 EARLY_HINTS per RFC 8297
• Adds 426 UPGRADE_REQUIRED per RFC 7231

v2.2.0: http-status-codes 2.2.0

Compare Source

• Adds 421 MISDIRECTED_REQUEST per RFC 7540

v2.1.4: http-status-codes 2.1.4

Compare Source

Introduced some non-breaking changes to the module in order to take better advantage of tree-shaking as suggested in #​55 and #​58.

This should reduce file size for most users who are able to take advantage of tree shaking, especially those who are only using a subset of this library's features.

Thanks to @​EvgenyOrekhov and @​OliverJAsh for their suggestions and feedback on these issues.

https://bundlephobia.com/result?p=http-status-codes@2.1.4

v2.1.3: http-status-codes 2.1.3

Compare Source

• Fix an issue where the common.js bundle was not working with react native projects. #​60 #​56
• Mark the module as "side-effect free" for tree shaking #​58

v2.1.2: http-status-codes 2.1.2

Compare Source

Exports ESM module for browser environments which fixes #​56

Provides a default export for additional backwards compatibility with v1 #​54

v2.1.1: http-status-codes 2.1.1

Compare Source

Fixes a bug with the way the TypeScript definitions were being built. #​52

Thanks to @​Benno007 for finding and reporting this issue.

v2.1.0: http-status-codes v2.1.0

Compare Source

• Adds a new status code: 451 Unavailable For Legal Reasons

Thanks @​ffflorian for this contribution.

v2.0.0: http-status-codes v2.0.0

Compare Source

This release marks a new major version of http-status-codes.

Improvements include:

• Project rewritten in TypeScript
• TypeScript enums "StatusCodes" and "ReasonPhrases"
• Test coverage
• Automated source code generation of codes and documentation
• Change the reason phrase "Server Error" to the correct one, "Internal Server Error"
• Rename "getStatusText" -> "getReasonPhrase" to make the API more consistent

Thanks to @​seanmhanson for their help on this new version.

Migrating from v1.x.x

http-status-codes v2 is mostly backwards compatible with v1. There is a single breaking change and two recommended changes.

[Breaking Change] 'Server Error'

The reason phrase for the status code 500 has been changed from "Server Error" to "Internal Server Error". This is the correct phrase according to RFC7231. If you are migrating from v1, and have code that relies on the result of getStatusText(500) or getReasonPhrase('Server Error'), then this could affect you.

[Non-breaking change] getStatusText renamed getReasonPhrase

The function getStatusText has been renamed to getReasonPhrase. The old function is still available, but may be deprecated in a future version. To fix this simply rename instances of getStatusText() to getReasonPhrase(). The function is otherwise the same as it was before.

[Non-breaking change] StatusCodes

In http-status-codes v1, Status Codes were exported directly from the top-level module. i.e. HttpStatus.OK. In v2 all Status Codes live under an object called StatusCodes. i.e. HttpStatus.StatusCodes.OK. We made this change to cater to TypeScript users who prefer a dedicated value with an enum type. The previous values are still exported, but we won't continue to update them. Please migrate if you're using the old-style imports.

---

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 was generated by Mend Renovate. View the repository job log.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the http-status-codes dependency from version 1.3.0 to 2.0.0. This is a major version update that includes breaking changes, such as renaming 'Server Error' to 'Internal Server Error' for the 500 status code, renaming getStatusText to getReasonPhrase, and changing the way status codes are accessed.

Class diagram showing http-status-codes v2 API changes

classDiagram
    class HttpStatusCodes {
      +StatusCodes
      +ReasonPhrases
      +getReasonPhrase(code)
      +getStatusText(code) deprecated
    }

    class StatusCodes {
      +OK: 200
      +CREATED: 201
      +INTERNAL_SERVER_ERROR: 500
    }

    class ReasonPhrases {
      +OK: 'OK'
      +CREATED: 'Created'
      +INTERNAL_SERVER_ERROR: 'Internal Server Error'
    }

    HttpStatusCodes --> StatusCodes
    HttpStatusCodes --> ReasonPhrases

    note for HttpStatusCodes "Major changes in v2:\n- getStatusText renamed to getReasonPhrase\n- Status codes moved under StatusCodes enum\n- 500 reason changed to 'Internal Server Error'"

Loading

File-Level Changes

Change	Details	Files
Updated the http-status-codes dependency to version 2.0.0.	Updated the http-status-codes dependency in package.json. Updated the http-status-codes dependency in package-lock.json.	package.json package-lock.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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!