- Is mrgoodbytes8667/pluralize-bundle a Laravel package?
- No. Despite the Composer name, it is a Symfony bundle that registers a Twig extension proxying Illuminate\Support\Pluralizer. There is no Laravel service provider, so package auto-discovery will not register it. Laravel apps can only use it by manually wiring the Twig extension through TwigBridge.
- How do I install and register the pluralize bundle in Symfony?
- Install it with composer require mrgoodbytes8667/pluralize-bundle, then enable it in config/bundles.php. The bundle registers a Twig extension and a container service so the pluralize and singular helpers are available in templates. Check the composer.json constraints first, because the declared PHP, Symfony, and illuminate/support ranges are unverified.
- Can I use this pluralize helper in Laravel Blade templates?
- Not directly. The package ships a Twig extension, so it only works where Twig is the template engine. Blade-only Laravel apps should use Str::plural(), Str::singular(), or the @choice directive instead. Using this bundle in Laravel requires TwigBridge and manual extension registration.
- Which PHP, Symfony, and Laravel versions does this bundle support?
- The constraints are not documented in the overview and should be treated as unverified. Run composer why-not mrgoodbytes8667/pluralize-bundle with a target version and inspect the composer.json before adopting it. A narrow illuminate/support constraint can block a framework major upgrade, so pin the exact version you tested.
- Does it pluralize based on a count, like 1 item versus 2 items?
- The wrapper pluralizes a bare string through Illuminate\Support\Pluralizer and does not provide count-aware formatting. Producing 1 item versus 2 items requires you to pass the count and format the number yourself. For ICU-style plural rules, use Twig's trans filter or a translation layer instead.
- Does this bundle support non-English languages or irregular nouns?
- No. The underlying Illuminate pluralizer is English-only and rule-based, so non-English locales and irregular or uncountable nouns can produce wrong output without raising an error. Silent failure is the riskiest kind in a template layer. If the app is multi-locale, pluralization belongs in the translation layer, not a string helper.
- What license is pluralize-bundle released under?
- Tooling reports the license as NOASSERTION, meaning it could not be identified automatically. Most organizations treat that as a hard gate until legal clears the LICENSE file. It also flags in SCA and SBOM tooling, so confirm compatibility before commercial or closed-source distribution.
- Is mrgoodbytes8667/pluralize-bundle actively maintained?
- Signals are weak: zero stars, zero dependents, a single maintainer, and a last release in December 2023. There is no documented security response path and the bus factor is one. For production, pin the version or vendor-fork the code and take ownership of fixes yourself.
- What are the alternatives to this Twig pluralize bundle?
- In Symfony, use EnglishInflector from symfony/string, already a transitive dependency in most installs, wrapped in a small Twig extension. In Laravel, wrap Str::plural() directly in a local Twig extension or use Blade's @choice directive. Both avoid pulling illuminate/support into Symfony and keep dependency constraints aligned with the framework.
- Should I use this package in production or write my own Twig pluralize extension?
- Build-versus-buy favors building: the equivalent is roughly a 30-line in-house Twig extension. That size makes the third-party dependency more governance cost than implementation cost. If you must use it, pin the exact version and fork it into src/ or a private VCS mirror rather than relying on upstream fixes.