- What is pragmarx/support used for in Laravel?
- It provides lightweight helper classes and utilities for Laravel applications, covering filesystem, string, array, environment, config, and cache tasks. It is shared across PragmaRX packages, so it often appears as a low-level support dependency. Review the source for the exact helpers you need before adopting it directly.
- How do I install pragmarx/support with Composer?
- Install it with composer require pragmarx/support. Laravel package auto-discovery should register any service provider if one is present, but confirm that in the package composer.json. Pin an exact version and run your application test suite after installation.
- Does pragmarx/support support Laravel 10 and Laravel 11?
- The package had a release in May 2024, which suggests recent Laravel compatibility, but you should check the composer constraints for exact Laravel and PHP versions. Do not assume Laravel 10 or 11 support without validating the require block and running tests in a sandbox. If the constraints block your Laravel version, avoid forcing the dependency.
- Is pragmarx/support already included by other PragmaRX packages?
- Run composer why pragmarx/support or composer show --tree to see whether another PragmaRX package already pulls it in. Because it is shared across PragmaRX components, it is often transitive rather than a direct choice. If it is already present transitively, retain and pin it instead of adding a duplicate direct requirement.
- Should I use pragmarx/support directly or write my own helpers?
- Adopt it directly only when a specific helper solves a concrete problem you cannot implement cleanly in a few lines. The package is a utility toolkit, not a framework, so many helpers are easy to reproduce internally. If you do adopt it, wrap usage behind an internal adapter so it can be replaced later.
- What PHP versions does pragmarx/support require?
- The exact PHP requirement is defined in the package composer.json, so check that file and the release constraints before installing. The May 2024 release is a positive signal, but it does not guarantee support for every PHP version. Validate compatibility with your application's PHP version in a sandbox first.
- Does pragmarx/support have tests and active maintenance?
- Public signals are weak: the package has modest stars, zero listed dependents, and likely single-maintainer stewardship, so test coverage and response time are uncertain. Inspect the repository tests and recent commit history rather than relying on the description. Budget for reading and patching the source if needed.
- How risky is adopting pragmarx/support in production?
- Risk is moderate: abandonment, Laravel and PHP upgrade incompatibility, autoload conflicts, and undocumented breaking changes are the main concerns. Mitigate with exact version pinning, CI coverage, dependency monitoring, and an internal adapter. Treat it as a narrowly scoped or transitive dependency, not a platform bet.
- How can I check if pragmarx/support is a transitive dependency?
- Use composer why pragmarx/support to see which installed package requires it, and composer show --tree for a visual dependency path. Run a full composer audit as part of the check. If no package requires it, you are considering a direct adoption rather than an inherited dependency.
- What are alternatives to pragmarx/support for Laravel helper utilities?
- For most helper tasks, Laravel's built-in Str, Arr, File, and Cache utilities or Symfony components are sufficient. If you need a maintained third-party toolkit, evaluate packages with active dependents and clear test coverage. Compare the exact helper you need against a small internal implementation before adding a dependency.