Hyphenator Bundle Laravel Package

Product Decisions This Supports

• Typography quality in long-form content surfaces. Hyphenation matters most where text is narrow or justified: mobile article views, multi-column PDFs, invoices/receipts, email templates, e-readers/EPUB exports, and print-style reports. If your roadmap includes any of these, this is a real (if small) quality lever — ragged right edges and mid-word overflow on long German/Finnish/Dutch terms are visible defects users report.
• Server-side vs. client-side rendering trade-off. Browsers do hyphenation natively via hyphens: auto plus a correct lang attribute. Any surface that doesn't run a modern browser engine — PDF generators (DomPDF, wkhtmltopdf), email clients, EPUB, server-rendered image cards/OG previews — cannot rely on CSS. That's the only place this decision genuinely bites.
• Build vs. buy vs. skip. This package represents the "buy" option (a Symfony bundle wrapping Org_Heigl_Hyphenator). Given its status, the real decision is skip or build a ~50–100 line service wrapper around the underlying library. Treat typographic polish as a small, bounded scope item — not a dependency worth architectural debate.
• i18n/locale roadmap input. Hyphenation is per-locale dictionary work. If you're expanding into German, Dutch, Swedish, Finnish, or Russian markets, add "text rendering quality" as an acceptance criterion in that locale launch checklist rather than a standalone feature.
• Legacy maintenance budgeting. If you already ship this bundle, this assessment is a de-risking signal: schedule replacement before a PHP/Symfony upgrade forces it, not during one.

When to Consider This Package

Consider it only in one narrow case:

• You maintain a legacy Symfony 2.x/3.x application that already depends on it, you're not upgrading PHP or Symfony this cycle, and rewriting the hyphenation call site would add risk for zero user-visible benefit right now.

Look elsewhere — or skip entirely — in every other case:

• New builds, or anything on Symfony 4+/5+/6+/7+ and PHP 8. Archived since 2015, last release 2015-10-24, zero dependents, 20 stars. No PHP 8 compatibility guarantees, no security response, no upstream fixes. A Composer constraint here is a future install failure waiting for a quiet Friday.
• Web-rendered content. Use CSS hyphens: auto with correct lang attributes. Zero dependencies, better performance, browser dictionaries are well maintained. This covers the majority of "we should hyphenate" requests.
• PDF/report generation. Prefer the renderer's built-in hyphenation (Prince, WeasyPrint, wkhtmltopdf all support it) or call org_heigl/hyphenator directly through a thin wrapper you own. Skip the Symfony bundle layer entirely — the bundle adds DI configuration and a Twig filter, which is roughly the code you'd write yourself in an afternoon.
• Bundle-fatigue check. A single-purpose bundle for a single library call is a poor dependency trade even when healthy. Weigh it against ~1 day of in-house work you fully control.
• If you need active maintenance signals (security policy, recent commits, PHP version matrix, issue response) — this fails on all of them; that's disqualifying for anything customer-facing at scale.

How to Pitch It (Stakeholders)

To executives: We evaluated a library for improving text layout in narrow and print-style surfaces. It's deprecated, archived since 2015, and has no active users or maintainers — adopting it would create an unsupported dependency with no security response path. The recommendation is to not adopt. Where the need is real, we get the same outcome from browser-native CSS at zero cost, or from a small in-house wrapper (~1 day of engineering) around the underlying hyphenation library for PDF and email surfaces. Net: no roadmap impact, no new vendor risk, one small optional scope item if a locale launch requires it.

To engineering: Do not add liip/hyphenator-bundle to any new or upgraded application. For legacy apps already using it, keep it until the next Symfony/PHP upgrade, then replace with a thin service wrapping org_heigl/hyphenator directly — the bundle contributes DI wiring and a Twig filter, nothing you can't own in under 100 lines. For web surfaces, delete the dependency and use hyphens: auto with correct lang attributes. For PDF/email, prefer the renderer's native hyphenation before writing anything.

Decision: Rejected for adoption. Logged as a known legacy dependency; replacement scoped as a ~1-day cleanup item, not a project.