chore(deps-dev): bump http-status-codes from 1.3.2 to 2.1.4

[dependabot-preview]

Bumps http-status-codes from 1.3.2 to 2.1.4.

Release notes

Sourced from http-status-codes's releases.

http-status-codes 2.1.4

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

http-status-codes 2.1.3

• 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

http-status-codes 2.1.2

Exports ESM module for browser environments which fixes #56

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

http-status-codes 2.1.1

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

Thanks to @Benno007 for finding and reporting this issue.

http-status-codes v2.1.0

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

Thanks @ffflorian for this contribution.

http-status-codes v2.0.0

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.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)