- What is rafrsr/resource-bundle used for in Laravel?
- rafrsr/resource-bundle is a lightweight Composer package for uploading, saving, and managing application resources as entities. In Laravel projects it is intended to organize resource-related logic behind a reusable bundle rather than ad hoc controller code. The public overview is brief, so confirm the exact resource model and storage behavior against the source before adopting it.
- How do I install rafrsr/resource-bundle with Composer?
- Install it as a normal Composer dependency, for example composer require rafrsr/resource-bundle. Because the 3.0.0 release note only mentions Symfony 4 support, check the resolved symfony/* and PHP constraints before committing the lock file. Run composer why-not rafrsr/resource-bundle if resolution fails in an existing Laravel application.
- Which Laravel versions are compatible with rafrsr/resource-bundle 3.0.0?
- The package is described for Laravel and Symfony integration, but no supported Laravel version matrix is published in the available notes. The Symfony 4 bump suggests alignment with Laravel 5.6 through 6.x era applications, though that is directional rather than confirmed. Verify the composer.json constraints and test on your exact Laravel version before upgrading.
- Does rafrsr/resource-bundle 3.0.0 require Symfony 4 and PHP 7.1.3 or higher?
- The 3.0.0 release note says it bumps support for Symfony 4, and Symfony 4 requires PHP 7.1.3 or later. It is not documented whether Symfony 3.4 remains supported alongside Symfony 4. Treat the PHP floor and Symfony constraint as items to confirm in the package manifest before planning an upgrade.
- Is rafrsr/resource-bundle only for Laravel or can I use it with Symfony?
- The overview and blurb describe integration with both Laravel and Symfony projects, and the package evidently layers on Symfony components used by Laravel. That makes it a plausible fit for Symfony applications as well, but the documented usage is thin. Validate service provider or bundle registration behavior in each framework before relying on it.
- What breaking changes are in rafrsr/resource-bundle 3.0.0?
- The only available release evidence is a one-line note: bump support for Symfony 4. A major version usually signals a breaking change, most likely a shifted Symfony constraint and possibly a higher PHP requirement. There is no published changelog or upgrade guide in the provided context, so inspect the diff and public API signatures before upgrading.
- How do I configure rafrsr/resource-bundle after installing it?
- Configuration details are not covered in the available overview, so start by checking composer.json for Laravel auto-discovery via extra.laravel and for a service provider. Look for publishable config with php artisan vendor:publish and review any package config keys before wiring uploads or storage paths. If the package assumes fixed paths or facade access, adjust your application layout rather than editing vendor code.
- Can I use rafrsr/resource-bundle in production?
- It can be evaluated for production, but the available evidence does not include a test matrix, CI status, or adoption data. Pin the exact version, run composer why-not against your Laravel and Symfony constraints, and add regression tests around upload, storage, and entity persistence. Treat the upgrade as a validation project rather than a drop-in replacement until the maintainer confirms the support matrix.
- What are alternatives to rafrsr/resource-bundle for managing resources in Laravel?
- Common alternatives include Laravel's native filesystem and storage APIs, Spatie's laravel-medialibrary for media attachments, and custom Eloquent models with observers or policies for resource lifecycle logic. The right choice depends on whether you need a general resource entity abstraction or a focused file upload and media library. Compare maintenance activity, Laravel version support, and test coverage before switching.
- How is rafrsr/resource-bundle maintained and tested?
- The provided assessment notes low-to-moderate confidence because there is no dependency manifest, changelog, test-coverage signal, or adoption data in the evidence base. The 3.0.0 release is described only as a Symfony 4 support bump, and the test matrix is not documented. Before depending on it, check the repository's CI configuration, release tags, Packagist support block, and recent commit activity.