- What is spawnrad/data-bundle and what problem does it solve?
- It is a lightweight package for defining reusable, structured data bundles so payloads for API responses, view data, and internal service calls are declared once instead of scattered arrays and ad-hoc DTOs. Bundles are composable, so small focused pieces can be nested and merged into larger payloads with predictable keys and getters. Treat it as a minimal utility rather than a full data-mapping framework, and read the source first because documentation is thin.
- How do I install spawnrad/data-bundle in a Laravel application?
- Install it with composer require spawnrad/data-bundle, then check whether the package ships a Laravel service provider for auto-discovery or a Symfony bundle class that would need manual registration. If config or migration stubs exist, publish them with php artisan vendor:publish and select the package tag. Run the install in an isolated spike branch rather than directly in a production service.
- Is spawnrad/data-bundle a Laravel package or a Symfony bundle?
- The overview describes it as Laravel-native, but the SPDataBundle repository name, the Bundle suffix, and a truncated French description suggest a possible Symfony origin. Inspect composer.json for illuminate/support and a ServiceProvider class versus symfony/framework-bundle and a class extending Bundle. Until that audit is done, treat the Laravel compatibility claim as unvalidated.
- Which Laravel and PHP versions does spawnrad/data-bundle support?
- There is no documented version matrix, CI badge, or release cadence, so the composer.json constraints are the only source of truth. Compare those constraints against your pinned PHP version and Laravel major before committing to anything. Because the package has zero known dependents, any claimed support may never have been exercised on current releases.
- How do I define, nest, and merge data bundles?
- Extend the package's base bundle class, declare your keys and getters, then compose nested bundles and merge them into a parent payload. The fluent, container-resolved API is designed to keep payload shapes predictable and type-safe across layers. Since there is no README-level guide, read src/ to confirm the exact extension contract before building on it.
- How do I publish and configure spawnrad/data-bundle?
- If the package includes a Laravel service provider and config stubs, run php artisan vendor:publish and choose its tag to copy the configuration into config/. If no provider or config file exists, there is nothing to publish and any configuration must be done in code. Verify this against the repository rather than assuming config keys exist.
- How does spawnrad/data-bundle compare to spatie/laravel-data or plain DTOs?
- All three target typed, reusable payloads, but spatie/laravel-data has wide adoption, solid documentation, and an active release history, while spawnrad/data-bundle has zero stars, no dependents, and no visible test suite. The package is smaller and pulls in nothing beyond Laravel core, which can suit a vendor-and-own approach. For most teams, plain readonly DTOs or spatie/laravel-data remain the lower-risk defaults.
- How do I test data bundles in a Laravel application?
- Write your own feature and unit tests that assert the exact keys and values your bundles produce, rather than inheriting any claims from the package. Cover nesting and merge behavior explicitly, since composition is where key collisions and shape drift tend to appear. If the repository ships tests, run them locally on your PHP and Laravel versions first to see whether they pass at all.
- Is spawnrad/data-bundle safe to use in production?
- There is no evidence of a test suite, CI pipeline, tag history, or community scrutiny, and the bus factor is one, so do not add it as a tracked dependency you expect upstream to maintain. If you adopt it, vendor or fork the code, review it for obfuscated logic, unexpected network calls, and post-install scripts, then run your own test pass. Prove it in an isolated spike before it touches a production service.
- Is spawnrad/data-bundle actively maintained?
- Nothing in the available signals suggests active maintenance: zero stars, zero dependents, no documented release cadence, and a truncated description that hints at broader documentation gaps. Check the last commit date, tags, and open issues before making any commitment. Plan to own the code outright, because upstream fixes and compatibility updates are not a reasonable expectation at this signal level.