Download the PHP package emkcloud/livewire-tweak without Composer
On this page you can find all versions of the php package emkcloud/livewire-tweak. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
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 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.
Informations about the package livewire-tweak
Livewire Tweak
Custom tweaks for Livewire and Flux
Blade directives, script output, and internal behavior have been adjusted. Custom prefixes were added to the default assets to ensure proper use in load-balanced environments.
Why this package exists
I built this package based on my experience working with clients who use firewalls and traffic load balancers that rely on custom URL prefixes such as /admin, /backend, /customers, etc.
In these environments, using popular Laravel packages like Nova, Livewire, or others can be problematic, because they often rely on absolute paths for assets and internal API calls.
Features
- Livewire Core Prefix
- Livewire Core Middleware
- Livewire Flux Prefix
- Livewire Flux Middleware
Requirements
- Laravel ^12
- Livewire ^3.6
- Livewire Flux ^2.0 (optional)
- Livewire Flux PRO ^2.0 (optional)
Installation
Configuration
The configuration file is optional. You can simply define the variables directly in your .env file. However, if you need to customize the options, you can publish the configuration file:
All options in the package have default values, so you only need to define the ones you want to customize in your configuration file.
Environment
To view all available variables and their meanings, refer to the following file:
Environment variables
License
The MIT License (MIT). Please see the package License file for more information.
