- How do I install daikazu/bladewind in a Laravel application?
- Install the package with Composer using composer require daikazu/bladewind, then follow the package's publish steps for any config or assets. After publishing, include the Bladewind Blade components or CSS directives in your layout as documented. Check the README for exact vendor:publish tags, since asset setup can vary by package version.
- Which Laravel versions does Bladewind support?
- Bladewind is built for Laravel Blade applications, but the exact supported Laravel and PHP versions are defined in its composer.json. Check that file or the Packagist listing before installing it in older or newly upgraded Laravel projects. For production, pin a version that you have tested against your application's Laravel release.
- How does Bladewind serve per-page CSS from an existing Vite build?
- Bladewind splits CSS rules from your existing Vite build and serves each Blade page only the rules that page uses. Your assets can still be compiled with Vite during build or deployment, while the package handles per-page CSS delivery without Node on the server. This helps reduce CSS payloads without requiring a Node process in production.
- Do I need Node.js or npm on the production server to use Bladewind?
- No. Bladewind is designed to serve per-page CSS split from your existing Vite build without requiring Node on the server. You can run Vite during your normal build or deployment pipeline, then let the package deliver the generated CSS in production. Confirm your deployment process still publishes the compiled assets correctly.
- Can I use Bladewind components with Tailwind CSS in Laravel Blade views?
- Yes. Bladewind provides ready-to-use Blade UI components such as buttons, modals, tables, and alerts styled with Tailwind CSS, so you can include them directly in Blade views. You still manage Tailwind as part of your Vite build, while Bladewind handles component markup and per-page CSS serving. This keeps the component layer server-rendered and avoids an extra JavaScript framework.
- How do I configure which CSS rules Bladewind includes per page?
- Bladewind derives per-page CSS from the rules each page actually uses, split from your Vite build, so configuration usually involves pointing it at your compiled CSS and including the package's Blade directives. Review the published config file for paths and build integration options. Test representative pages to confirm that each response includes the expected rules and no unnecessary CSS.
- Is Bladewind a replacement for Livewire, Alpine.js, or a JavaScript framework?
- Bladewind focuses on Blade UI components styled with Tailwind CSS and per-page CSS delivery. It does not require an extra JavaScript framework, but it is not a replacement for Livewire or Alpine.js when your application needs reactive or complex client-side behavior. Use it for server-rendered Blade interfaces and add JavaScript tooling only where interactivity requires it.
- How should I test Bladewind components and per-page CSS in a Laravel app?
- Write Laravel feature tests that render pages using Bladewind components and assert that the expected markup and CSS references appear. For per-page CSS, verify that each response includes only the stylesheet or rules associated with that page rather than the full build. Add a test for a page with minimal components to catch over-inclusion.
- What production deployment concerns apply to Bladewind's per-page CSS?
- Build your Vite assets during deployment, then let Bladewind serve the split per-page CSS at runtime without Node on the server. Watch for cache invalidation when CSS changes, and make sure your web server or CDN serves generated stylesheets with appropriate caching headers. After each deploy, test key pages to confirm the per-page rule split matches the current build.
- What alternatives exist to Bladewind for Laravel Blade UI components and per-page CSS?
- Alternatives include Blade UI Kit for Blade components, Tailwind UI or Flux for styled component libraries, and CSS purging tools for reducing stylesheet size. Bladewind's distinction is serving per-page CSS split from your Vite build without Node on the server. Compare component coverage, Tailwind version support, and maintenance activity before choosing.