- What is igdr/resource-bundle used for?
- It is described as a Laravel bundle for building resource-oriented applications, offering reusable resource classes, transformations, and controller patterns aimed at API and CRUD work. The public description stops there, so the exact problem domain has to be confirmed by reading the source. There is no usage evidence, documentation, or dependent package that clarifies its intended scope.
- Is igdr/resource-bundle a Laravel package or a Symfony bundle?
- The Composer name follows Laravel vendor/package convention, but the Bundle suffix and the ResourceBundle repository name echo Symfony terminology. Check composer.json for illuminate/* or laravel/framework requirements and for a Laravel service provider with auto-discovery before assuming drop-in support. If it is Symfony-style, it does not fit a Laravel application without a bridge layer.
- Which Laravel and PHP versions does igdr/resource-bundle support?
- No version support matrix is published, and the package has zero dependents, so it has never been exercised against real Laravel upgrades. Inspect the php and laravel/framework constraints in composer.json directly. Treat it as incompatible with your current LTS until a time-boxed spike proves otherwise.
- How do I install igdr/resource-bundle?
- Installation follows the standard Composer path: run composer require igdr/resource-bundle in an isolated branch. Because no documentation exists, confirm whether a service provider is auto-discovered, whether a config file should be published, and whether a facade is registered. Run composer show --tree afterward to review the transitive dependency surface.
- Is igdr/resource-bundle safe for production use?
- There is no evidence of an active maintainer, production usage, or security patch history, and a package with zero stars and zero dependents carries high abandonment and supply-chain risk. Read every file before letting it autoload in your runtime, confirming there are no network calls, eval usage, or remote class loading. If adopted, fork it into your own namespace and pin a tagged version instead of depending on upstream directly.
- Does igdr/resource-bundle ship tests and documentation?
- No tests, changelog, or meaningful README content are evident from the public information available. That means there is no semver signal to rely on and onboarding cost is close to reverse-engineering the source. Budget audit time accordingly before promising a delivery date.
- How does igdr/resource-bundle compare to Laravel's built-in API Resources?
- Laravel ships JsonResource, ResourceCollection, and API resource classes that are first-party, maintained, and documented, which covers most transformation and serialization needs. Any third-party bundle has to justify itself against that baseline plus maintained options such as Spatie packages. Ask what specific problem this package solves that those do not.
- Can igdr/resource-bundle scaffold CRUD controllers and API transformations?
- The blurb advertises reusable resource classes, transformations, and controller patterns for API and CRUD development, which suggests that intent. However, no examples or API reference exist to confirm actual behaviour or whether any code generation is involved. Validate the primary use case end-to-end in a spike branch before committing.
- What should I check in the composer.json before adopting igdr/resource-bundle?
- Confirm the php constraint, laravel/framework or illuminate/* constraints, PSR-4 autoloading correctness, and the license. Run composer show --tree to flag unmaintained transitive dependencies and composer outdated for version drift. These checks are prerequisites, not optional due diligence.
- How do I remove the abandonment risk of igdr/resource-bundle?
- Fork the repository into your internal Git namespace, tag a version, and point Composer at the fork through a VCS repository or private Packagist. Wrap all package calls behind your own interface so replacement becomes a single-file change. That converts an unmaintained third-party dependency into an internally controlled one.