tyhpdef / composer-class-map-generator
Tyhp type definitions for composer/class-map-generator 1.7.3.
Package info
github.com/tyhpproject-packages/composer-class-map-generator
Type:metapackage
pkg:composer/tyhpdef/composer-class-map-generator
Requires
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
tyhpdef/composer-class-map-generator
Tyhp type definitions for composer/class-map-generator 1.7.3.
composer require --dev tyhpdef/composer-class-map-generator:1.7.3
This is a metapackage. Composer also installs tyhpdef/composer-class-map-generator-impl (type files).
Require this name, not tyhpdef/composer-class-map-generator-impl.
See https://tyhplang.com.
Maintain composer/class-map-generator? Ship the types yourself
If you are a Packagist maintainer of composer/class-map-generator, you can take over these
types.
Copy _tyhpdef/ from tyhpdef/composer-class-map-generator-impl (Apache-2.0; keep the NOTICE).
Then either:
- Bundle the files in
composer/class-map-generatorand setextra.tyhp.packageon thatcomposer.json, plus"replace": { "tyhpdef/composer-class-map-generator": "self.version" }, or - Publish a sibling types package under your vendor, versioned with
composer/class-map-generator(sameX.Y.Z). Setextra.tyhp.packagethere,requirecomposer/class-map-generatorwith a real constraint,"replace": { "tyhpdef/composer-class-map-generator": "self.version" }, and setextra.tyhp.tyhpdefoncomposer/class-map-generatorto 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/composer-class-map-generator Packagist name.
Full process: TYHPDEF_OWNERSHIP.md in
https://github.com/tyhpproject/tyhp-runtime-src