Weave Code
Support Laravel Package
arcanedev/support
ARCANEDEV Support provides shared helpers and utilities for ARCANEDEV and Laravel projects. A lightweight toolkit of common support classes and convenience functions, compatible across Laravel 5.1 through 10.x.
:muscle: Support package is a collection of helpers and tools for ARCANEDEV + Laravel projects.
Frequently asked questions about Support
- What Laravel versions does arcanedev/support support?
- The package officially supports Laravel 5.1 through 10.x, as indicated in the README. Always check the latest release notes for version-specific changes or breaking updates, especially if you're using Laravel 9.x or 10.x.
- How do I install arcanedev/support in my Laravel project?
- Run `composer require arcanedev/support` in your project root. The package registers its service provider automatically, so no additional manual configuration is required unless you need customization. Verify the `SupportServiceProvider` appears in `config/app.php`.
- Does this package include Blade directives, and how do I use them?
- Yes, the package provides Blade directives like `@supportAlert()` and `@supportButton()`. These are registered automatically. Use them in your Blade templates as you would native directives, but test them across themes to ensure styling and accessibility compliance.
- Are there any performance concerns with using arcanedev/support helpers?
- The package includes utility methods like `Support::slugify()` and `Support::randomString()`, which are optimized for performance. However, benchmark critical helpers (e.g., in loops) against your existing implementations to ensure no regressions, especially in high-traffic applications.
- Can I override or extend the package’s default behavior?
- Yes, most features can be customized via configuration files or by binding overrides in your `AppServiceProvider`. For example, you can replace the default `apiResponse()` format by publishing the package’s config and modifying it. Check the package’s documentation for specific extension points.
- Does arcanedev/support work with other ARCANEDEV packages like arcanedev/log?
- Yes, the package is designed to integrate seamlessly with other ARCANEDEV tools, such as `arcanedev/log`. Some features may require dependencies like `arcanedev/log` for full functionality, so review the package’s documentation or source code for interdependencies.
- How do I test arcanedev/support in my Laravel application?
- The package includes unit tests, but you should also write integration tests to validate its behavior in your specific context. Test Blade directives in isolated views, API response helpers in controller methods, and utility functions in edge cases (e.g., non-ASCII input for `slugify()`).
- Are there any known conflicts with existing Laravel packages or custom code?
- Potential conflicts may arise if your project already includes similar helper methods (e.g., custom `slugify()` functions) or if the package’s service provider duplicates registrations. Review the package’s source code and check for naming collisions before integration.
- What if I need a feature not included in arcanedev/support?
- The package is open-source and accepts contributions. Submit a feature request via GitHub Issues or create a pull request following the [contribution guidelines](https://github.com/ARCANEDEV/Support/blob/master/CONTRIBUTING.md). The maintainers are responsive, as indicated by active issue tracking.
- How do I handle security updates or breaking changes in arcanedev/support?
- Monitor the package’s [GitHub Releases](https://github.com/ARCANEDEV/Support/releases) and [Changelog](https://github.com/ARCANEDEV/Support/blob/master/CHANGELOG.md) for updates. The MIT license allows forks if maintenance stops, but consider contributing to the project or setting up CI checks to catch breaking changes early in your pipeline.
Weaver
How can I help you explore Laravel packages today?