Weave Code
Template Extension Bundle Laravel Package
os2display/template-extension-bundle
A PHP/Symfony bundle for OS2display that adds template extension functionality, enabling developers to define, manage, and integrate custom display templates within the OS2display platform. Streamlines extending template options for digital signage and screen content.
Extends os2display/core-bundle with extra tools for templates
Frequently asked questions about Template Extension Bundle
- Is os2display/template-extension-bundle a Laravel package?
- No. Although it is installable through Composer, it is a Symfony bundle from the OS2display digital signage platform, so it ships DependencyInjection extension classes and Twig namespaces rather than a Laravel ServiceProvider. Laravel will not autodiscover it and there is no config file to publish. Treating it as a drop-in Laravel dependency is the most common evaluation mistake. If your runtime is Symfony the fit is natural; if it is Laravel, budget for a port.
- How do I install os2display/template-extension-bundle?
- Run composer require os2display/template-extension-bundle, register the bundle in config/bundles.php on Symfony, and configure it under the bundle's extension alias. Pin the exact 2.1.0 version rather than a caret range until asset and cache behaviour is understood. Check the composer require block for the actual PHP, symfony/* and twig/twig constraints before pinning. There is no Laravel package discovery step to rely on.
- What is new in version 2.1.0?
- 2.1.0 is a minor, additive release whose only referenced change is PR #2, feature: Darkmode tool. No deprecations or breaking changes were disclosed. The release note does not say whether the tool lands as a Twig function or filter, a config flag under the bundle alias, a CSS/JS asset, or a per-template toggle. Confirm which one before integrating, because each has a different integration path and blast radius.
- Can I use this bundle in a Laravel application?
- Not directly. You have three realistic paths: a Twig bridge plus manual container wiring, extracting just the dark mode logic and assets into a Blade directive or view composer, or running a sidecar Symfony service for template rendering. Extracting the logic is usually cheapest and removes upstream update tracking; the sidecar is only justified if you need the full template-extension semantics. Pick one explicitly rather than discovering it mid-sprint.
- What PHP, Symfony and Twig versions does it require?
- The 2.1.0 release notes disclose no constraint changes, but a bundle feature often rides a raised minimum, so read the composer require block in the repository. Verify PHP, symfony/* and twig/twig constraints against your runtime before pinning. Also confirm whether 2.1.0 is a clean upgrade from whatever you run today, since a 1.x to 2.x hop may already have been breaking. Do not assume the minor bump tells the whole compatibility story.
- Is dark mode opt-in or a global default?
- Semver-minor implies backward compatibility, so existing template rendering should be unaffected as long as dark mode is opt-in. That said, a template extension bundle sits directly on the output path, and changes to shared templates or macros can alter markup for every consumer even without opting in. Confirm whether the toggle is per template, per tenant, or a global default before rolling it out. If it involves server-side colour resolution rather than a CSS class toggle, the risk profile is higher.
- Do I need to republish assets or clear caches after upgrading?
- Possibly. If the dark mode tool ships CSS or JS it likely assumes a specific asset builder such as Webpack Encore or Vite, and a mismatched pipeline gives you a silent no-op rather than a hard failure. Check whether 2.1.0 requires republishing assets and whether it changes cache keys. Enable the feature in one non-production template and diff the rendered output against your 2.0.x baseline first.
- How do I test for rendering regressions after upgrading?
- Pin 2.1.0, publish and verify assets, enable dark mode in a single non-production template, then diff the rendered markup against your previous baseline before expanding. Because the bundle touches shared templates and macros, diff unrelated templates too, not just the one you toggled. Treat 2.1.0 as a trial dependency for one release cycle rather than making it load-bearing for a customer-facing theme. Keep the pinned version in place until asset and cache behaviour is confirmed.
- Is this package actively maintained?
- A 2.1.0 release whose only referenced change is PR #2 suggests a young or recently re-homed repository. That is a maturity flag rather than a defect, but it changes how much you should lean on upstream. Check the maintainer list, the release cadence, and whether a changelog exists beyond PR titles before adopting. If you fork or vendor, you take ownership of future fixes.
- What are the license and vendoring terms?
- Read the license file in the repository before vendoring or forking, since redistribution terms determine whether you can ship a modified copy inside your product. If you port only the dark mode logic into a Blade directive, keep the original attribution intact. Forks remove upstream update tracking, so budget time for owning that code long term.
Weaver
How can I help you explore Laravel packages today?