Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Supports Laravel Package

yansongda/supports

Supports is a small PHP utility library from the yansongda ecosystem that simplifies working with arrays, configuration, and pipelines. It provides handy helpers for array access and manipulation, config handling, and pipeline processing, making it useful for Laravel or PHP projects that need lightw...

View on GitHub
Deep Wiki
Context7

handle with array/log/config/guzzle etc.

Frequently asked questions about Supports
What is yansongda/supports used for?
Supports is a small framework-agnostic PHP utility library that provides helpers for arrays, configuration, pipelines, JSON encoding and decoding, and HTTP request traits. It is designed as a lightweight support layer for PHP applications rather than a full framework. In Laravel projects it can serve as shared glue for API clients, data transformers, and reusable service classes.
Does yansongda/supports work with Laravel?
Yes, it is framework-agnostic but aligns with Laravel's trait-driven architecture and includes a Laravel-style pipeline abstraction. It does not ship a Laravel service provider, config publishing, or container bindings, so you must wire those yourself if needed. It is suitable for Laravel 11 and 12, and Laravel 10 only where PHP 8.2 is already deployed.
How do I install yansongda/supports with Composer?
Install it with composer require yansongda/supports. The package requires PHP 8.2 or higher, so confirm your runtime before adding it. There are no config files to publish or service providers to register for the standalone utilities.
What PHP version does yansongda/supports require?
The current release requires PHP greater than or equal to 8.2. That effectively gates it to Laravel 11 and 12, with Laravel 10 supported only when PHP 8.2 is already in place. Services still on PHP 8.0 or 8.1 are blocked until they upgrade.
Do I need a service provider to use yansongda/supports in Laravel?
No service provider is included, and none is required for static helpers such as the JSON utility. If you want container bindings or facades, you must write and register your own service provider. The HasHttpRequest trait also needs explicit mixin or container wiring when used in Laravel.
How does the Json helper differ from native json_encode and json_decode?
The Json helper is a thin, exception-first wrapper over native JSON functions. Json::encode defaults to JSON_UNESCAPED_UNICODE, while native json_encode defaults to no flags, and Json::decode defaults to associative arrays. Json::decode throws JsonException on invalid input instead of returning null, so controllers and jobs need explicit error handling.
Can I use the yansongda/supports pipeline without Laravel?
Yes, the package provides a Laravel-style pipeline abstraction that can be used standalone in any PHP project. It is useful for reusable request or data processing chains without depending on Illuminate\Pipeline. If Laravel's pipeline is already available, the marginal benefit is mainly consistency rather than new capability.
Is yansongda/supports still maintained?
Yes, the assessment notes v4.1.3 published on 2026-10-10, which materially resolves earlier stale-maintenance concerns. However, release notes and examples are Chinese-only, so onboarding and support expectations should account for that. Review the v3.x and v4.x changes before committing to an upgrade path.
What are the risks of using the HasHttpRequest trait in a large codebase?
HasHttpRequest still requires explicit mixin or container wiring. In large codebases, trait methods can collide with existing methods and pollute classes that mix it in. Prefer composition or isolated API client classes if you need stricter boundaries and easier testing.
What changed between yansongda/supports v2, v3, and v4?
The jump from v2.2.0 to v4.1.3 spans v3.0.0, which removed logging, and v4.0.0, whose contents are not covered in the provided release notes. A full diff review and changelog check are mandatory before treating this as a routine upgrade. Because of the PHP 8.2 hard gate, it may be more accurate to treat the move as a re-adoption decision.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
socialdept/atp-orm
cboxdk/laravel-assistant-client
socialdept/atp-resolver
socialdept/tenant-domains
tautvydasr/blade-class-names
socialdept/color-scales
maherelgamil/controller
coleus/widgets
coleus/table
coleus/users
coleus/music
coleus/health
coleus/calendar
coleus/notes
coleus/support
coleus/settings
coleus/apps
seampact/laravel
emmyconceptng/laravel-ng-postcode
jjsquady/round-robin