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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
http-status-codes	^1.3.2 -> ^2.0.0

---

Release Notes

prettymuchbryce/http-status-codes

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.

v1.4.0

Compare Source

• Add a getStatusCode function [#​28]

---

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.