Weave Code
Shared Bundle Laravel Package
ranky/shared-bundle
Ranky SharedBundle provides reusable services, configuration, and common helper code for Ranky PHP projects. It gives applications and companion bundles a consistent shared foundation, reducing duplication and simplifying maintenance across the ecosystem.
ranky/shared-bundle is a reusable Symfony bundle that centralizes common code shared across Ranky projects. It provides a consistent foundation for shared services, configuration, and domain utilities, reducing duplication and keeping applications aligned.
- Reusable services and helpers for Ranky applications
- Shared configuration and bundle defaults
- Common domain utilities and reusable components
- Consistent integration patterns across projects
- Simple Composer installation and Symfony bundle registration
Frequently asked questions about Shared Bundle
- What is ranky/shared-bundle used for?
- Ranky Shared Bundle is described as a reusable Symfony bundle that provides shared components and common utilities for Ranky PHP applications. Its purpose is to centralize shared configuration, services, and integrations so multiple projects avoid duplication. The supplied materials do not confirm that it is Laravel-native, so treat it as a shared Composer dependency whose integration details must be verified in the repository.
- Does ranky/shared-bundle work with Laravel?
- Laravel compatibility is not confirmed by the supplied overview or release evidence. The package is described as a Symfony bundle, and it may still be consumable by Laravel if it declares compatible illuminate/* constraints and registers a Laravel service provider. Check composer.json, package discovery metadata, and a test installation before planning adoption in a Laravel application.
- How do I install ranky/shared-bundle with Composer?
- The mechanical installation is composer require ranky/shared-bundle, followed by resolving the package in each consuming application. You must then confirm whether the package is auto-discovered or requires a manual provider or bundle registration entry. Do not assume Symfony bundle registration or Laravel package discovery; inspect the package metadata and provider code first.
- What changed in ranky/shared-bundle version 2.1.2?
- The supplied evidence for v2.1.2 is only a compare link from v2.1.1 to v2.1.2, with no enumerated commits, changelog body, or migration notes. The patch version implies no intended API change, but that is a weak signal rather than a validated diff. Request commit subjects or review the compare diff before treating the release as understood.
- Is ranky/shared-bundle v2.1.2 safe for production?
- It is low risk by semantic versioning because it is a patch release, but it is unverified in practice. An empty or opaque changelog means you cannot tell whether the release is a typo fix, a dependency constraint change, or something with broader impact. Gate production adoption on a diff review and constraint check, and use a pin-and-audit policy if the maintainer will not enumerate changes.
- Which PHP and Laravel versions does ranky/shared-bundle support?
- The supported PHP and Laravel version ranges are not stated in the supplied materials. Inspect the package composer.json for php, illuminate/support, illuminate/database, and related constraint ranges, then compare them with your application matrix. This is a quick check that determines whether integration is trivial or incompatible before any work is scheduled.
- Does ranky/shared-bundle publish config, migrations, or translations?
- The supplied release notes do not say whether the package publishes configuration, migrations, translations, or other assets. Shared bundles sometimes do, and any such changes can require re-publishing and review in every consuming application. Check the service provider boot method and documented publish tags, and confirm whether v2.1.2 altered any publishable files.
- Is ranky/shared-bundle auto-discovered in Laravel?
- Auto-discovery is not confirmed by the supplied evidence. Symfony bundles are typically registered in bundles.php, while Laravel packages use extra.laravel.providers in composer.json or a manual provider entry in config/app.php. Inspect the package metadata and provider registration before assuming discovery works.
- How should I test or roll out a ranky/shared-bundle update?
- Create a dedicated pull request per consuming application containing only the lockfile change plus composer why output so any regression bisects cleanly to the bump. Run your CI matrix across supported PHP and Laravel versions, then observe the application in a staged environment. Because a shared bundle sits on the dependency path of every consumer, a regression can affect all applications at once.
- What maintenance and alternative concerns apply to ranky/shared-bundle?
- Ask who owns the package upstream, whether there is a second maintainer, what the release cadence is, and whether the repository has a CI matrix that ran green for the tag. Also count how many applications depend on it directly and transitively, because that defines the blast radius of a bad patch. Alternatives depend on scope: a private monorepo, split packages, or a Laravel-specific shared package may fit better if Symfony-origin coupling is a problem.
Weaver
How can I help you explore Laravel packages today?