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