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