Weave Code
Wire Core Laravel Package
nyoncode/wire-core
Core foundations for the nyoncode/wire package family, offering shared utilities, helpers, and base abstractions that simplify building Laravel and Livewire applications while keeping wire-powered projects consistent.
nyoncode/wire-core is the foundational package for Laravel applications and packages built around the Wire ecosystem. It centralizes shared contracts, configuration, and service-provider wiring, giving dependent packages a consistent base while keeping their own code focused and lightweight.
- Modular service provider with sensible defaults
- Publishable configuration for app-level customization
- Shared contracts and utilities for reuse across packages
- Laravel auto-discovery and extensible architecture
Frequently asked questions about Wire Core
- What is nyoncode/wire-core and what problem does it solve?
- nyoncode/wire-core is the foundational package for Laravel applications and packages built around the Wire ecosystem. It centralizes shared contracts, configuration, and service-provider wiring so dependent packages get a consistent base. It includes a modular service provider with sensible defaults, publishable configuration, shared contracts and utilities, and Laravel auto-discovery.
- How do I install nyoncode/wire-core in a Laravel application?
- Install it with composer require nyoncode/wire-core. Laravel auto-discovery should register the service provider if the package declares extra.laravel.providers. Before committing, verify whether a tagged semver release exists or whether Composer resolves to dev-main, and inspect the require block for laravel/framework and php constraints.
- Does nyoncode/wire-core support Laravel 10 and Laravel 11?
- The package targets modern Laravel and Livewire applications, but the repository does not publish explicit version-support documentation as of this evaluation. You should inspect the composer.json require block to confirm the laravel/framework and php ranges match your stack. If constraints are absent or too broad, you are effectively testing it against every framework minor you upgrade to.
- Is nyoncode/wire-core auto-discovered by Laravel, or do I need to register the service provider manually?
- Laravel auto-discovery is part of the package design via the extra.laravel.providers entry, so you typically do not need to add the provider to config/app.php manually. If discovery is not configured in the version you install, register the provider explicitly. Confirm the provider class name in the source since published documentation is not yet available.
- How do I publish the configuration file for nyoncode/wire-core?
- The package supports publishable configuration for app-level customization, typically through php artisan vendor:publish with the package provider tag. Run vendor:publish with the provider option and select the wire-core config tag. Because documentation is absent, check the service provider publishes method for the exact tag and config key.
- What contracts and utilities does nyoncode/wire-core provide?
- It centralizes shared contracts and utilities intended for reuse across Wire packages, plus base abstractions that simplify building Laravel and Livewire applications. The source is effectively the spec right now, so read the contracts directory and service provider to see what is actually available. Focus on the subsystems you need, such as actions, modals, notifications, or design tokens, rather than adopting the whole surface.
- Can I use nyoncode/wire-core with existing Livewire base components?
- You can compose its traits into an existing base component, but trait method collisions are the highest-probability failure mode because Laravel fatals on duplicate trait methods at class-load time. Audit method names in your current base class against the package traits before mixing them in. A safer evaluation path is to reimplement the two or three patterns you need inside your own primitives layer.
- Is nyoncode/wire-core production-ready, and are there tagged releases?
- The architecture fits a shared foundation, but the artifact is not yet a foundation: at evaluation time it had zero stars, zero dependents, no published documentation, and no evident CI or release history. Treat it as a reference implementation until you confirm tagged semver releases and pinned framework constraints. If only dev-main is available, you cannot constrain it with a caret range, and any upstream commit can land on the next composer update.
- What are the alternatives to nyoncode/wire-core?
- The main alternative is pattern adoption: read the MIT-licensed traits and actions, then reimplement the few ideas worth keeping inside your own base abstractions. That gives you zero dependency risk and no fork obligation while capturing the architectural insight. Other options include building your own service provider and contracts layer, or using more established Laravel starter kits and Livewire scaffolding packages.
- What are the main risks of depending on nyoncode/wire-core?
- Ranked risks are trait method collisions at boot, unpinned dev-main distribution without changelogs or semver, unconstrained Laravel and PHP requirements, hidden container coupling through service-provider bindings, and a bus factor of one. Mitigate by verifying tagged releases and require constraints, auditing trait methods, and keeping the wrapper from leaking deeply into application code. If the package stalls, the fork-or-remove cost depends on how tightly you coupled to its bindings.
Weaver
How can I help you explore Laravel packages today?