Tinymce Bundle Laravel Package

Product Decisions This Supports

• Laravel editor standardization: Unchanged. This remains a Symfony bundle with no service provider, config publishing, Blade components, or Laravel conventions. v3.0.5 adds nothing that supports a Laravel adoption decision.
• Framework target and modernization: This release materially changes the framework story: the symfony/framework-bundle constraint is bumped to 7.*, so the bundle now targets Symfony 7, not Symfony 2. That reframes the build-vs-buy question — it is no longer only a legacy bridge, but it also means it is not usable on Symfony 2/3/4/5/6. Treat the earlier "legacy Symfony2 stopgap" framing as obsolete.
• Build vs. buy vs. wrap: Still favors wrapping the official TinyMCE distribution, a maintained framework integration, or a small internal Blade/Livewire (or Twig) component. A dependency whose only current release change is a version constraint is not a differentiated capability.
• Vendor and maintenance risk assessment: Reinforced, not resolved. Still 0 stars and 0 dependents, and v3.0.5 is a single constraint-only PR from a first-time contributor. Low activity plus a hard major-framework constraint is a signal to inspect composer.json and CI before relying on it.
• Migration scoping: Adjust plans that assumed this bundle could carry legacy editors forward. Upgrading to v3.0.5 forces Symfony 7; staying on older Symfony means pinning to v3.0.4 or earlier. Neither path is a strategic migration answer — the editor integration itself is small enough to own.
• Roadmap prioritization: Unchanged. Rich-text editing is commodity capability; a constraint-bump release is not a reason to spend roadmap capacity.

When to Consider This Package

Consider it only when:

• You are on Symfony 7 (or actively migrating to it) and want a pre-built TinyMCE wiring rather than writing it yourself.
• You need a quick, low-effort TinyMCE integration for an admin or content-authoring screen and are comfortable owning the wrapper.
• You have verified the 7.* constraint against your actual Symfony version and PHP version, and confirmed the release changes nothing beyond that constraint.
• The integration is time-boxed and replaceable, with a clear path to an in-house component or the official TinyMCE distribution.
• You have reviewed the package source, release provenance, and TinyMCE's own license terms.

Look elsewhere when:

• You are building or maintaining a Laravel application — unchanged; this package provides no Laravel integration.
• You are on Symfony 6 or earlier — this release will not install; the legacy line is v3.0.4 and older, which is a maintenance dead end.
• You need a maintained, community-validated dependency. Zero stars, zero dependents, and a one-line release remain weak ecosystem evidence.
• You require long-term security support or an active maintainer response path; a constraint-only release is not evidence of either.
• You need a modern editor experience with first-class framework integration. Prefer the official TinyMCE package, Filament rich editor, Livewire/Blade or Twig components, or alternatives like Tiptap or CKEditor.
• You need cloud collaboration, accessibility compliance, or enterprise support — go to TinyMCE's commercial offerings.

How to Pitch It (Stakeholders)

Executive summary: v3.0.5 is a version-constraint update that moves this bundle onto Symfony 7. It is still not a Laravel package, still has no visible adoption, and its only recent change is a dependency bump. The decision is unchanged for Laravel: do not adopt. For Symfony 7 teams, treat it as an optional convenience wrapper — likely cheaper to inline than to depend on — and do not plan migrations around it.

For engineering: The release raises symfony/framework-bundle to 7.*, which is a breaking constraint for anyone on older Symfony and effectively retires the legacy-Symfony use case this package was previously evaluated for. Verify composer.json, the supported PHP range, and TinyMCE version assumptions before a spike. If a Symfony 7 app needs TinyMCE, a short internal Twig/asset integration or the official TinyMCE package carries less risk than a zero-adoption third-party bundle.

Recommendation: Do not adopt for Laravel. For Symfony 7, evaluate only as a time-boxed convenience with an explicit replacement path; the scope of what it saves is small. For new work in either framework, build a thin integration around the official TinyMCE distribution or select a maintained, framework-native rich-text solution.