Download the PHP package ttbooking/vite-manager without Composer
On this page you can find all versions of the php package ttbooking/vite-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ttbooking/vite-manager
More information about ttbooking/vite-manager
Files in ttbooking/vite-manager
Package vite-manager
Short Description Vite Application Manager for Laravel.
License MIT
Informations about the package vite-manager
Laravel Vite Manager
This package extends Vite functionality built in Laravel, so you can manage multiple entry point (hereafter app) configurations without clogging your Blade templates with clumsy configuration code. It is especially useful if your project have multiple JS entry points, or if you develop a package which publishes its own Vite managed assets.
Installation
You can install this package using Composer:
Then you'll probably need to publish configuration file:
Configuration
There are 3 ways to configure Vite "apps".
Config file
The most basic way. Use it if you develop a project with few entry points.
Example config/vite.php
file:
You may find complete list of configurable options here.
Note VITE_APP
environment variable, which you can use to customize default entry point per environment:
Service provider's boot
method
Advanced method. Use it if you develop a package with Vite assets, or if you need fine-grained control over your app configuration:
You can use your AppServiceProvider.php
(or other of your choice) for this matter, but it is recommended to use
separate provider, especially if you have many entry point configurations. Just don't forget to register this service
provider in your config/app.php
file.
App factory
The most advanced method. Use it if you have many similar apps/workspaces to be configured alike:
Closure passed into useAppFactory
retrieves 4 arguments: a Vite
class instance to be configured by the factory,
app name, corresponding configuration section (if exists), and application's container instance.
You may (or may not) want to amend instance's configuration by the options from config file.
To do this, call configure
method on Vite
instance with the given $config
variable.
This way, end user could change predefined options on per-app basis.
Usage
@viteApp
directive should be used in Blade templates:
If you are using template engine other than Blade, you can use vite_app
helper function:
If you are using TwigBridge, don't forget to register this function in
config/twigbridge.php
file under extensions.functions
section.