Weave Code
Helpers Laravel Package
elasticms/helpers
PHP Helpers wraps and simplifies common PHP functions into PHPStan-compliant helpers, making static analysis easier and code safer across elasticMS projects. Part of the elasticMS monorepo, with docs and issue tracking available on GitHub.
[READONLY] enclose regular PHP functions in PHPStan compliant functions
Frequently asked questions about Helpers
- Is elasticms/helpers a Laravel package or a framework-agnostic PHP library?
- It is a framework-agnostic PHP helper library, not a structurally Laravel-specific package. It does not appear to ship a service provider, config file, facade, or container bindings. It can install into a Laravel application if the Composer PHP constraints match, but Laravel integration is incidental rather than a declared feature.
- How do I install elasticms/helpers in a Laravel project?
- Install it with Composer using composer require elasticms/helpers, then pin the exact version you have tested. Because releases appear to track the elasticMS release train rather than an independent semver contract, avoid loose constraints. After installation, swap only bounded call sites and run your existing tests against the changed failure paths.
- Does elasticms/helpers provide a Laravel service provider, facade, or config file?
- There is no evidence of a Laravel service provider, facade, config file, or container binding in the package framing. It is described as a collection of PHPStan-compliant helper functions wrapping native PHP functions. Treat it as a plain Composer dependency and do not expect Laravel auto-discovery or publishable configuration.
- Which Laravel and PHP versions are supported by elasticms/helpers?
- The package is aimed at PHP 8.x codebases and is not presented as having Laravel-version-specific support. Laravel 10, 11, and 12 applications should be able to install it only if the package composer.json PHP constraint matches your runtime. Check the actual composer.json and test on your PHP 8.3 or 8.4 target before adopting it.
- Are the elasticms/helpers functions global, namespaced, or static class methods?
- The documentation describes helper functions, but it does not confirm whether they are global functions, namespaced free functions, or static class methods. This matters because namespaced functions require use function imports in every file and global functions create collision risk. Confirm the callable style and namespace before any pilot.
- What happens when a wrapped PHP function fails in elasticms/helpers?
- The failure contract must be confirmed from the source because wrappers often narrow native union return types by throwing instead of returning false or null. That is a behavioral change: code that checked for false from file_get_contents or json_encode may now take an exception path. Test every swapped call site that can fail and identify the exception types thrown.
- Is elasticms/helpers PHPStan-friendly, and does it include a PHPStan extension?
- The package markets itself as PHPStan-compliant, but there is no evidence of a separate PHPStan extension or stub file. The value appears to come from annotations shipped directly in the helper source. Confirm which PHPStan major version the annotations target, since PHPStan 1.x and 2.x annotation semantics can differ.
- Can I use elasticms/helpers alongside Larastan, Str, Arr, and Collection?
- Yes, it can coexist technically, but avoid adopting it for string and array manipulation where Laravel's Str, Arr, and Collection already have Larastan-compatible annotations. The narrower fit is native calls that return broad unions, such as JSON encoding, filesystem reads, regex matching, URL parsing, and unserialize. Use it selectively rather than as a repository-wide replacement for native PHP calls.
- Is LGPL-3.0 safe for a commercial Laravel application using elasticms/helpers?
- LGPL-3.0 is unusual for a PHP utility library and may be on organizational blanket-ban lists. For internal SaaS use it is often acceptable, but redistributed or on-premises-shipped products may trigger relinking and notice obligations. Record the license in your compliance review before adoption and do not rely on informal assumptions.
- Is elasticms/helpers maintained and production-ready, or should I build my own helpers?
- It appears to be an internal elasticMS monorepo utility that happens to be published, with issues tracked in the elasticMS repository and releases tied to that project. There is no independent semver contract, so pin versions and verify whether bugs receive a response. For production, run a bounded pilot and compare it with a small in-house wrapper set whose failure behavior you control.
Weaver
How can I help you explore Laravel packages today?