tyhpdef / dompdf-dompdf
Tyhp type definitions for dompdf/dompdf 3.1.6.
Package info
github.com/tyhpproject-packages/dompdf-dompdf
Type:metapackage
pkg:composer/tyhpdef/dompdf-dompdf
Requires
- tyhpdef/dompdf-dompdf-impl: ~3.1.6.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
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:
- Bundle the files in
dompdf/dompdfand setextra.tyhp.packageon thatcomposer.json, plus"replace": { "tyhpdef/dompdf-dompdf": "self.version" }, or - Publish a sibling types package under your vendor, versioned with
dompdf/dompdf(sameX.Y.Z). Setextra.tyhp.packagethere,requiredompdf/dompdfwith a real constraint,"replace": { "tyhpdef/dompdf-dompdf": "self.version" }, and setextra.tyhp.tyhpdefondompdf/dompdfto 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