Weave Code
Tabler Bundle Laravel Package
survos/tabler-bundle
Symfony bundle that integrates the Tabler admin dashboard UI kit, providing Twig templates, layouts, navigation/menu helpers, and asset setup so you can quickly build Bootstrap-based admin interfaces.
Theme using tabler.io
Frequently asked questions about Tabler Bundle
- What does survos/tabler-bundle actually do?
- It is a Symfony bundle that packages the Tabler.io Bootstrap admin dashboard UI kit, shipping Twig templates, base layouts, navigation and menu helpers, and asset setup so you can build admin screens quickly. It is not documented as a Laravel package: there is no confirmed service provider, facade, publishable config, or Blade integration. Treat it as a Symfony/Twig front-end template and asset bundle until you have read the source tree and composer.json. The only confirmed capability today is that it installs from Packagist.
- Does survos/tabler-bundle work with Laravel?
- There is no documented Laravel or illuminate/* support, and the bundle is built around Twig rather than Blade, so Blade templates will not run its Twig views directly. You could port the markup and partials into Blade layouts manually, but that is custom work, not an integration the package provides. Verify composer.json require constraints against your Laravel version before assuming anything works.
- How do I install survos/tabler-bundle?
- Installation follows standard Composer flow with composer require survos/tabler-bundle at a pinned major such as ^2.0, followed by registering the bundle in a Symfony application and wiring its asset setup. The 2.0 release is the first tagged Packagist version, so there is no earlier install pattern to compare against. In a Laravel app, expect to evaluate the package in a throwaway branch or scratch project rather than dropping it into production.
- Which PHP and Laravel versions does survos/tabler-bundle support?
- This is the biggest unknown: the package does not document PHP or framework version constraints in the material available. Pin an explicit major instead of floating, then run composer why-not against your framework and PHP version to surface conflicts early. Also check the lockfile delta and transitive dependency weight, because a package that pulls in several new libraries changes the risk profile.
- Why is the first release of survos/tabler-bundle numbered 2.0?
- A first Packagist release labelled 2.0 implies either a pre-Packagist history you cannot see or a versioning discipline you cannot rely on. Either way, a constraint like ^2.0 may not mean what you assume it means for future upgrades. Plan now for the fact that a future 3.0 would be your first real breaking-change event.
- Is survos/tabler-bundle safe to use in production?
- Treat it as high risk driven by unknowns rather than known defects: single maintainer, first tagged release, terse release notes, and no visible test suite, CI badge, static analysis, or security disclosure path. There is no prior assessment baseline, so no dependency audit or maintainer track record exists to lean on. The one genuine upside is that with no existing adoption, your upgrade cost is zero, so the entire cost is the initial bet. Do not read installs from Packagist as vetted engineering readiness.
- Can I use the Tabler templates with Blade instead of Twig?
- The bundle ships Twig templates, so Blade support is not something it offers out of the box. Tabler itself is Bootstrap-based, so the HTML markup and CSS classes transfer cleanly, but the layout inheritance and navigation helpers are Twig and PHP specific and would need rewriting. For many teams it is faster to take the upstream Tabler static template and build a single Blade layout around it.
- What are good alternatives to survos/tabler-bundle for a Laravel admin dashboard?
- If you specifically want the Tabler look, pull the Tabler HTML template or its npm/CDN assets and wrap them in a Blade layout, which is a small, well-understood job. If you want a batteries-included Laravel admin panel, look at Filament, Laravel Nova, Orchid, or Backpack instead, all of which document Laravel version support and have established maintenance. The bundle is only worth adopting if its Twig layouts and menu helpers save you meaningful work you cannot reproduce quickly.
- How should I evaluate survos/tabler-bundle before depending on it?
- Use a staged approach with cheap exit points. Start with a read-only audit of the repository, composer.json, license, tests, issue history, and release cadence, with no install. Then spike it in a scratch app matching your framework version to confirm it boots cleanly with no service-provider side effects, and only then try one non-critical path on an evaluation branch while checking that the resolution graph is clean.
- Is survos/tabler-bundle a thin wrapper I could reimplement myself?
- Very likely yes, given it mainly packages an existing open-source UI kit plus Twig layouts and menu helpers on top. That matters because abandonment risk is the classic profile for single-maintainer first releases, and reimplementation cost is your fallback if it disappears. Before adding the dependency, confirm whether the navigation and asset helpers justify the maintenance and versioning risk versus simply vendoring Tabler's static assets.
Weaver
How can I help you explore Laravel packages today?