Weave Code
Ui Laravel Package
nuewire/ui
nuewire/ui is a Laravel package that provides a set of reusable Blade UI components, helping you build clean, consistent interfaces faster with minimal markup and sensible defaults.
nuewire/ui is a lightweight, Blade-first UI component library for Laravel that helps you build clean, consistent interfaces without leaving your templates. It ships with ready-to-use Blade components and sensible defaults, so you can compose forms, layouts, and interactive elements in minutes while keeping full control over markup and styling.
- Blade components for forms, buttons, modals, and layouts
- Tailwind-friendly styling with straightforward overrides
- Zero configuration setup via package discovery
- Accessible markup and keyboard-friendly interactions
- Customizable slots and attributes on every component
Frequently asked questions about Ui
- How do I install nuewire/ui in a Laravel project?
- Install it with Composer using composer require nuewire/ui, then check the package README for any publish tags and run php artisan vendor:publish for the ones it provides. Before installing, run composer why-not nuewire/ui 1.0.1 in the target app to surface PHP and Laravel version conflicts early. Confirm the declared support matrix in the package's composer.json rather than assuming it matches your stack.
- Which Laravel and PHP versions does nuewire/ui support?
- The exact constraints are whatever composer.json declares at tag 1.0.1, and that file is the authoritative source since the release notes do not enumerate them. The package targets Laravel applications with Blade views and Livewire integration, so expect a Laravel support range plus a Livewire constraint if interactive components are included. Always verify with composer why-not before scheduling any work, because a mismatch here is the most common cause of unexpected integration delays.
- Do I need Livewire to use nuewire/ui?
- The package is described as UI components for Laravel and Livewire, so Livewire is part of the intended stack and some components may rely on it for interactivity. Purely presentational components are typically Blade-only and can be used without any Livewire component on the page. Check the individual component docs to see which ones require a Livewire context before removing the dependency from your app.
- Does nuewire/ui require Tailwind CSS?
- Packages of this type almost always target Tailwind, but the release material does not state which major version is pinned or whether precompiled CSS ships with the package. There are two possible setups: the package ships built assets you import, or your tailwind.config.js needs a content glob pointing at its view paths plus a rebuild step in CI. Confirm which case applies before you start, because the second path adds build pipeline work.
- How do I publish and customize the Nue UI components?
- Many Laravel UI packages are designed to be published into resources/views/vendor so you own and edit the markup locally, and that is the model to check for here. Run php artisan vendor:publish and look for tags covering views, config, and assets, then read the diff of anything published before editing. If views are meant to be published and owned locally, treat the published copies as your code and track changes when you upgrade.
- Is it safe to upgrade from nuewire/ui 0.0.1 to 1.0.1?
- A move from 0.x to 1.0.1 is a major bump, and semver explicitly permits breaking changes to Blade component names, slot names, props, and published view paths across that boundary. There is no published 1.0.0 release note in the available data, so first read the 0.0.1...1.0.1 diff and decide whether 1.0.1 is a patch on a stable 1.0.0 or a relabel. Also confirm whether any in-flight or production service already depends on 0.0.1; if so, halt and re-evaluate against the actual diff.
- Is nuewire/ui stable enough for production use?
- The integration surface is low risk because a UI component package lives in the presentation layer and should not touch domain logic, persistence, auth, or queueing. The weaker signal is process maturity: a 1.0.1 tag with a one-line changelog and no visible release history, CI badge, security policy, or upgrade guide. Treat the 1.0 version number as a statement of intent, pin the exact version in composer.json, and review the diff before each update.
- Where can I find the nuewire/ui changelog and release history?
- The captured release notes for 1.0.1 contain only a link to a diff against 0.0.1, and no CHANGELOG.md, UPGRADING.md, or security contact is referenced in the material reviewed. That means you cannot currently distinguish a documentation-only patch from a behavioural change by reading notes alone. Read the actual diff on the repository and check the repo root for changelog, upgrade, and security files before adopting or upgrading.
- What components does nuewire/ui actually include?
- The overview describes reusable UI components and ready-made Blade elements that reduce repetitive markup and keep styling consistent, but it does not enumerate the catalogue. Browse the repository's resources/views directory at tag 1.0.1 to see the concrete component names, props, and slots available. Confirm the list matches what your screens need before committing, since missing form or modal primitives would mean writing them yourself anyway.
- How does nuewire/ui compare to other Laravel UI component libraries?
- It occupies the same niche as Blade UI Kit, Flux, TallStackUI, and similar component packages, so the deciding factors are the component set, the Tailwind major it pins, the Laravel and Livewire range it supports, and how actively it is maintained. Nuewire UI reads as a small or solo-maintainer package, so weigh bus factor and release cadence alongside features. Read the diff at 1.0.1 and check test coverage and CI status before choosing it over a more established alternative.
Weaver
How can I help you explore Laravel packages today?