npm upgrade

http-status-codes 1 → 2

1.4.0 → 2.3.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.

http-status-codes 2.3.0 keeps every export lurq extracted, with the same argument counts.

Removed: 0
Renamed: 0
Signature changes: 0
Types removed: 0
Newly deprecated: 53
Added: 58

Does this break your code?

Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:

npx lurqrun check-upgrade --upgrade http-status-codes@1.4.0..2.3.0

To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:

npx lurqrun

Quickstart

Newly deprecated

Still exported in 2.3.0, marked deprecated.

ACCEPTED
BAD_GATEWAY
BAD_REQUEST
CONFLICT
CONTINUE
CREATED
EXPECTATION_FAILED
FAILED_DEPENDENCY
FORBIDDEN
GATEWAY_TIMEOUT
GONE
HTTP_VERSION_NOT_SUPPORTED
IM_A_TEAPOT
INSUFFICIENT_SPACE_ON_RESOURCE
INSUFFICIENT_STORAGE
INTERNAL_SERVER_ERROR
LENGTH_REQUIRED
LOCKED
METHOD_FAILURE
METHOD_NOT_ALLOWED
MOVED_PERMANENTLY
MOVED_TEMPORARILY
MULTIPLE_CHOICES
MULTI_STATUS
NETWORK_AUTHENTICATION_REQUIRED
NON_AUTHORITATIVE_INFORMATION
NOT_ACCEPTABLE
NOT_FOUND
NOT_IMPLEMENTED
NOT_MODIFIED
NO_CONTENT
OK
PARTIAL_CONTENT
PAYMENT_REQUIRED
PERMANENT_REDIRECT
PRECONDITION_FAILED
PRECONDITION_REQUIRED
PROCESSING
PROXY_AUTHENTICATION_REQUIRED
REQUESTED_RANGE_NOT_SATISFIABLE
REQUEST_HEADER_FIELDS_TOO_LARGE
REQUEST_TIMEOUT
REQUEST_TOO_LONG
REQUEST_URI_TOO_LONG
RESET_CONTENT
SEE_OTHER
SERVICE_UNAVAILABLE
SWITCHING_PROTOCOLS
TEMPORARY_REDIRECT
TOO_MANY_REQUESTS
UNAUTHORIZED
UNPROCESSABLE_ENTITY
UNSUPPORTED_MEDIA_TYPE

An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Sep 10, 2026. http-status-codes on lurq.