Search by

tyhpdef / dompdf-dompdf

pristinesource

Tyhp type definitions for dompdf/dompdf 3.1.6.

Package info

github.com/tyhpproject-packages/dompdf-dompdf

Type:metapackage

pkg:composer/tyhpdef/dompdf-dompdf

Statistics

Installs: 1

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

3.1.6 2026-10-05 14:40 UTC

This package is auto-updated.

Last update: 2026-10-05 14:41:17 UTC


README

tyhpdef/dompdf-dompdf

Tyhp type definitions for dompdf/dompdf 3.1.6.

composer require --dev tyhpdef/dompdf-dompdf:3.1.6

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

See https://tyhplang.com.

Maintain dompdf/dompdf? Ship the types yourself

If you are a Packagist maintainer of dompdf/dompdf, you can take over these types.

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

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

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