tyhpdef / psr-http-message

2.0 2026-10-05 18:57 UTC

Requires

• tyhpdef/psr-http-message-impl: ~2.0.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 18:58 UTC

README

tyhpdef/psr-http-message

Tyhp type definitions for psr/http-message 2.0.

composer require --dev tyhpdef/psr-http-message:2.0

This is a metapackage. Composer also installs tyhpdef/psr-http-message-impl (type files). Require this name, not tyhpdef/psr-http-message-impl.

See https://tyhplang.com.

Maintain psr/http-message? Ship the types yourself

If you are a Packagist maintainer of psr/http-message, you can take over these types.

Copy _tyhpdef/ from tyhpdef/psr-http-message-impl (Apache-2.0; keep the NOTICE). Then either:

1. Bundle the files in psr/http-message and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/psr-http-message": "self.version" }, or
2. Publish a sibling types package under your vendor, versioned with psr/http-message (same X.Y.Z). Set extra.tyhp.package there, require psr/http-message with a real constraint, "replace": { "tyhpdef/psr-http-message": "self.version" }, and set extra.tyhp.tyhpdef on psr/http-message to your sibling’s Composer name.

Ship that to Packagist first, then open an issue:

https://github.com/tyhpproject/tyhp-runtime-src/issues/new?template=tyhpdef-ownership.yml

We verify Packagist ownership and that the types parse and cover the PHP API, then stop publishing community tags for those versions. We do not transfer the tyhpdef/psr-http-message Packagist name.

Full process: TYHPDEF_OWNERSHIP.md in https://github.com/tyhpproject/tyhp-runtime-src