Weave Code
Avalynx Web Pack Laravel Package
jbsnewmedia/avalynx-web-pack
Laravel package that bundles the Avalynx frontend web components into your app, with asset publishing and Blade-friendly integration so you can add lightweight, dependency-free UI elements without a separate build setup.
An enhanced web application package built on top of the Symfony default skeleton.
Frequently asked questions about Avalynx Web Pack
- How do I install jbsnewmedia/avalynx-web-pack in a Laravel application?
- Install it with Composer by running composer require jbsnewmedia/avalynx-web-pack in your project root. The package's service provider is registered through Laravel's package auto-discovery, so no manual entry in config/app.php is usually required. After installation, publish the bundled assets with the Artisan publish command documented in the README so the compiled CSS and JavaScript land in your public directory.
- Which Avalynx components are included in this package?
- The bundle ships the Avalynx frontend library set in one install, including AvalynxUI, AvalynxSelect, AvalynxModal and additional Avalynx components. Because everything arrives as a single dependency, you do not have to require each Avalynx package individually. Check the package README for the exact component list and version of each library included in the current release.
- How do I publish the Avalynx assets to my Laravel public directory?
- Publishing is handled by an Artisan command that copies the compiled, versioned assets into your application's public path. Run the command shown in the package documentation, typically as part of your deploy script, so every environment receives the same asset set. The published files are plain CSS and JavaScript, so they can be served directly by Nginx, Apache or Laravel's public disk without further tooling.
- Do I need npm or a frontend build step to use Avalynx Web Pack?
- No. The package publishes precompiled assets, so you can add the Avalynx components to a Blade view without running npm, Vite or any bundler. This makes it a good fit for traditional Laravel applications, internal tools or admin panels where a full Node build pipeline is unnecessary. If you already use Vite, you can still import the published files or copy them into your own asset pipeline.
- Which Laravel versions does jbsnewmedia/avalynx-web-pack support?
- The package targets modern Laravel releases and relies on standard service provider auto-discovery, so it works on current Laravel versions without manual registration. Because supported versions change over time, check the require and require-dev constraints in the package's composer.json or the compatibility notes in the README before upgrading a major Laravel release. Running composer why-not jbsnewmedia/avalynx-web-pack is a quick way to see whether a version conflict is blocking installation.
- Does Avalynx Web Pack work with Blade views and Livewire components?
- Yes. The Avalynx components are framework-agnostic JavaScript, so they work inside normal Blade templates and alongside Livewire-rendered markup. For Livewire, initialize or re-initialize the components after a DOM update, for example in a Livewire hook or an Alpine-style event listener, so newly rendered elements pick up their behaviour. The package also publishes Blade directives to make including the assets in your layout simpler.
- How do I load the Avalynx CSS and JavaScript in my Blade layout?
- After publishing, reference the assets in your main layout using the Blade directives the package provides, or with a standard asset() helper call pointing at the published path. Place the stylesheet in the head section and the JavaScript before the closing body tag so components initialise after the markup exists. If you use a shared layout, add the directives once there rather than in every individual view.
- Should I install the Avalynx Web Pack bundle or the individual Avalynx packages?
- Choose the bundle when you want several Avalynx components available at once and prefer a single Composer dependency with one asset publishing step. Install individual packages instead if you only need one component and want the smallest possible footprint or independent version control per library. Both approaches expose the same framework-agnostic JavaScript, so switching later is mostly a matter of adjusting your asset includes.
- How do I update the published Avalynx assets after a Composer update?
- After running composer update, re-run the package's publish command so the public assets match the newly installed library version. Use the force flag if your publish command supports it and you want to overwrite previously published files, but keep any local customisations outside the published directory so they are not lost. Because published paths are versioned, stale browser caches are avoided as long as your layout references the current path.
- Is avalynx-web-pack safe for production and how do I handle browser caching?
- The package only ships static frontend assets plus a small Laravel service provider, so there is no runtime backend risk or external network call at request time. Because it has zero external dependencies and does not rely on a CDN, you control caching entirely through your web server or Laravel response headers. The versioned asset paths help with cache busting, so it is safe to serve the files with long max-age headers and refresh them only when you publish a new version.
Weaver
How can I help you explore Laravel packages today?