Download the PHP package admin9/blade-daisyui without Composer

On this page you can find all versions of the php package admin9/blade-daisyui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of admin9/blade-daisyui

Informations about the package blade-daisyui

Blade DaisyUI

Blade components for DaisyUI 5 — pure UI, zero business logic.

Provides 65 components as anonymous Blade views with a <x-dui::*> prefix, ready to drop into any Laravel 11/12 project that uses Tailwind CSS + DaisyUI 5.

Requirements

Installation

The package auto-discovers its service provider. No manual registration needed.

Usage

All components use the dui namespace:

Components (65)

Actions

accordion, alert, button, dropdown, fab, loading, modal, progress, radial-progress, skeleton, swap, toast, tooltip

Data Display

avatar, badge, card, carousel, chat, countdown, diff, kbd, list, stat, status, table, timeline

Data Input

calendar, checkbox, fieldset, file-input, filter, input, label, radio, range, rating, select, textarea, toggle, validator

Layout

collapse, divider, dock, drawer, footer, hero, indicator, join, mask, navbar, stack

Navigation

breadcrumbs, link, menu, pagination, steps, tab

Mockup

mockup-browser, mockup-code, mockup-phone, mockup-window

Effects

hover-3d, hover-gallery, text-rotate, theme-controller

Props Convention

Components accept DaisyUI modifier props directly:

Prop Type Description
color string DaisyUI color: primary, secondary, accent, info, success, warning, error
size string Size modifier: xs, sm, md, lg, xl
variant string Style variant: outline, soft, dash, ghost, link (component-specific)

All extra HTML attributes are forwarded to the root element via $attributes->merge().

Customizing Classes

Every component merges your classes with its defaults:

Visual Review

The package now includes curated example views under the blade-daisyui::examples.* namespace. Mount them in any Laravel app to exercise the components together and validate the visual hierarchy described in docs/visual-audit.md :

Use the docs/visual-audit.md checklist while stepping through both scenes so you notice density shifts, theme transitions, badge pressure, and form behavior before releasing component changes.

For component-level conclusions, see docs/component-audit.md. That file summarizes which high-frequency primitives are visually stable, which ones are easy to misuse, and where follow-up work is actually worth doing.

Recommended: Publish The Host Stubs

The package example views are content-only partials. The fastest way to use them in a real Laravel app is to publish the host wrapper views and the Tailwind/DaisyUI CSS stub:

This will publish:

The published wrapper views use:

If your app uses a different layout component or a section-based layout, just edit the published stubs and replace <x-layouts.app> with your preferred wrapper.

Minimal Host App Routes

Once the wrapper views are published, point routes to the host views instead of the package partials:

Minimal Host App Styling Requirements

The published CSS stub contains the required Tailwind + DaisyUI imports and scans the package Blade files:

Make sure your layout still loads the compiled assets, for example:

Testing

License

MIT. See LICENSE.md.

All versions of blade-daisyui with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/contracts Version ^11.0|^12.0
illuminate/support Version ^11.0|^12.0
spatie/laravel-package-tools Version ^1.16
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package admin9/blade-daisyui contains the following files

Loading the files please wait ...