tyhpdef / spatie-laravel-package-tools

1.93.2 2026-10-05 19:14 UTC

Requires

• tyhpdef/spatie-laravel-package-tools-impl: ~1.93.2.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 19:14 UTC

README

tyhpdef/spatie-laravel-package-tools

Tyhp type definitions for spatie/laravel-package-tools 1.93.2.

composer require --dev tyhpdef/spatie-laravel-package-tools:1.93.2

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

See https://tyhplang.com.

Maintain spatie/laravel-package-tools? Ship the types yourself

If you are a Packagist maintainer of spatie/laravel-package-tools, you can take over these types.

Copy _tyhpdef/ from tyhpdef/spatie-laravel-package-tools-impl (Apache-2.0; keep the NOTICE). Then either:

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

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