Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Ajaxcom Bundle

Ajaxcom Bundle Laravel Package

everlutionsk/ajaxcom-bundle

Everlution AjaxcomBundle integrates Ajaxcom JavaScript with Symfony and Twig, enabling AJAX-driven block rendering, flash messages, and configurable persistent or refreshable blocks for smoother frontend updates.

View on GitHub
Deep Wiki
Context7

Symfony 3 bundle for AjaxCom automation

Frequently asked questions about Ajaxcom Bundle
Is everlutionsk/ajaxcom-bundle a Laravel package?
No. It is a Symfony bundle documented for Symfony 2/3-era applications, registered through app/AppKernel.php and registerBundles(). Laravel has no bundle concept and will never call anything from it. Treat it as a reference implementation for an AJAX fragment pattern, not as a Laravel dependency.
Can I use everlutionsk/ajaxcom-bundle in a Laravel application?
Composer will install it, but nothing will be registered in Laravel's container. There is no service provider, facade, or config merge, so the bundle's Symfony services, Twig extensions, and event subscribers never run. Direct integration is not viable and any adoption requires porting the PHP side into Laravel-native code.
Which Laravel versions does everlutionsk/ajaxcom-bundle support?
None. The package targets Symfony, and its documented bootstrapping is Symfony 2/3-era AppKernel registration. It declares no Laravel support and ships no Laravel service provider. Every Laravel version, from 8 through 12, is unsupported.
How do I install and configure Everlution AjaxcomBundle in Symfony?
Run composer require everlutionsk/ajaxcom-bundle, then register Everlution\AjaxcomBundle\EverlutionAjaxcomBundle in registerBundles(). Install @everlutionsk/ajaxcom-js via npm and include build/ajaxcom.js in your Twig layout with the asset() helper, then add a JavaScript handler per the ajaxcom-js docs. Configuration is optional via everlution_ajaxcom, covering flash_template, flash_block_id, persistent_class, and blocks_to_render.
What does AjaxcomBundle actually do for AJAX block rendering?
It integrates the Ajaxcom JavaScript client with Symfony and Twig so the server returns HTML fragments for named blocks plus flash messages, which the client swaps into the DOM. Controllers can call addAjaxBlock and refreshAjaxBlock, and blocks_to_render can auto-render blocks on each AJAX request. Empty blocks are filtered out unless the refresh flag is set to true.
Is there a Laravel alternative to AjaxcomBundle for partial page updates?
Livewire is the closest Laravel-native option for server-driven component updates without a full SPA. HTMX with Blade fragments works well for simple partial swaps, and Inertia or Turbo Laravel cover SPA-style navigation. All are actively maintained and integrate with Laravel's container, routing, and session handling.
Can I use the @everlutionsk/ajaxcom-js client with Laravel and Vite?
The JavaScript client is the portable half of the project and can be installed via npm and bundled with Vite. However, the bundle assumes ajaxcom.js is served through Twig's asset() helper, so you must replace that include with a Vite entry. You also have to reverse-engineer the request and response envelope, because the wire format is undocumented.
Does AjaxcomBundle's Twig flash message handling work with Blade?
No. The bundle ships Twig flash templates and relies on Symfony's flash bag and Twig rendering, both of which differ materially from Laravel's session flash behavior and Blade. You would need to rebuild the flash payload and the template layer for Blade. The default flash_template and flash_block_id settings have no Laravel equivalent.
Is everlutionsk/ajaxcom-bundle safe for production and actively maintained?
The signals are poor: six stars, zero dependents, a single maintainer group, and a November 2024 tag on an API surface that remains Symfony 2/3-era. That recent release looks like housekeeping rather than modernization. Adopting it means you absorb all bug fixes, CSRF differences, and framework-version drift yourself.
How would I reimplement AjaxcomBundle's AJAX fragment protocol as a Laravel package?
Build a thin Laravel package with a service provider, a response factory that emits the fragment envelope, and middleware that piggybacks flash messages onto AJAX responses. First document or reverse-engineer the JSON schema, fragment identifiers, and flash payload used by @everlutionsk/ajaxcom-js. Then cover it with HTTP tests asserting the fragment HTML and response contract. This is modest, well-understood work and avoids depending on an abandoned Symfony bundle.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
coleus/frame
thtg88/journalism
filagora/filagora-ai-forums
rlacerda83/query-parser
socialdept/atp-orm
cboxdk/laravel-assistant-client
socialdept/atp-resolver
socialdept/tenant-domains
tautvydasr/blade-class-names
socialdept/color-scales
maherelgamil/controller
coleus/widgets
coleus/table
coleus/users
coleus/music
coleus/health
coleus/calendar
coleus/notes
coleus/support
coleus/settings