tyhpdef / mtdowling-jmespath.php

2.9.2 2026-10-05 18:30 UTC

Requires

• tyhpdef/mtdowling-jmespath.php-impl: ~2.9.2.0

Apache-2.0

• static analysis
• dev

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

README

tyhpdef/mtdowling-jmespath.php

Tyhp type definitions for mtdowling/jmespath.php 2.9.2.

composer require --dev tyhpdef/mtdowling-jmespath.php:2.9.2

This is a metapackage. Composer also installs tyhpdef/mtdowling-jmespath.php-impl (type files). Require this name, not tyhpdef/mtdowling-jmespath.php-impl.

See https://tyhplang.com.

Maintain mtdowling/jmespath.php? Ship the types yourself

If you are a Packagist maintainer of mtdowling/jmespath.php, you can take over these types.

Copy _tyhpdef/ from tyhpdef/mtdowling-jmespath.php-impl (Apache-2.0; keep the NOTICE). Then either:

1. Bundle the files in mtdowling/jmespath.php and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/mtdowling-jmespath.php": "self.version" }, or
2. Publish a sibling types package under your vendor, versioned with mtdowling/jmespath.php (same X.Y.Z). Set extra.tyhp.package there, require mtdowling/jmespath.php with a real constraint, "replace": { "tyhpdef/mtdowling-jmespath.php": "self.version" }, and set extra.tyhp.tyhpdef on mtdowling/jmespath.php 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/mtdowling-jmespath.php Packagist name.

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