- Is pdfloresjdav/alertify-bundle a Laravel package?
- No. It is a Symfony bundle that wires AlertifyJS into Symfony applications through bundle conventions, service container configuration, Twig helpers, and asset publication. Laravel does not provide those integration points natively, so the package is not a drop-in Laravel dependency. Treat it as a Symfony integration or a reference implementation for AlertifyJS configuration.
- Can I install alertify-bundle in Laravel with Composer?
- You can run Composer, but installing it does not give you a working Laravel integration. The bundle expects Symfony bundle registration, Twig, and Symfony asset conventions that Laravel does not supply out of the box. Direct installation would pull unnecessary Symfony components and still require custom adaptation. The practical approach is to use AlertifyJS directly through npm and Vite in Laravel.
- What does AvAlertifyBundle actually provide?
- The bundle provides Symfony-specific wiring around AlertifyJS, including service container configuration, Twig helpers or templates, and asset publication conventions. Its value is in Symfony integration rather than the underlying JavaScript library. AlertifyJS itself handles alerts, confirmations, prompts, and toast notifications in the browser. In Laravel, only the AlertifyJS assets and any thin configuration logic would be reusable.
- Does alertify-bundle support Laravel Blade and Vite?
- There is no native Blade or Vite support described for this Symfony bundle. It is built around Twig templates and Symfony asset publication, not Laravel's Blade views or Vite pipeline. You would need to reimplement any helper logic as Blade directives or components and load AlertifyJS through npm and Vite yourself. The package does not bridge those Laravel front-end conventions.
- What Laravel, PHP, and Symfony versions are supported?
- The provided context does not document supported Laravel, PHP, Symfony, or Twig versions, and compatibility with modern Laravel and PHP 8.x is unproven. The package is a Symfony bundle, so Laravel version support is effectively not applicable. Before considering any reuse, check the repository for Composer constraints, branch activity, and changelog details. Absent that information, assume version risk and pin carefully.
- Is pdfloresjdav/alertify-bundle actively maintained?
- The assessment reports zero stars and zero dependents, which is a weak maintenance and adoption signal. There is no evidence of active issue triage, community support, or downstream usage. The repository may be abandoned or stale, and its AlertifyJS version may be outdated. For production use, that single-maintainer risk should be weighed against the modest UI-notification value.
- Should I use this bundle or AlertifyJS directly in Laravel?
- For Laravel, use AlertifyJS directly through npm and Vite rather than adopting the Symfony bundle. The bundle's unique value is Symfony wiring, which Laravel cannot consume natively. Direct AlertifyJS usage gives you a framework-agnostic browser library with fewer PHP integration risks. Only vendor small pieces of the bundle if you find unique configuration logic worth keeping under the MIT license.
- How would I migrate from AvAlertifyBundle to AlertifyJS in Laravel?
- Do not migrate the bundle wholesale. Review it for the AlertifyJS version, default configuration, and any PHP-side helper logic, then install AlertifyJS directly via npm and load it through Laravel Vite. Reimplement only the alert, confirm, prompt, or toast behavior your application actually needs, preferably in a small Blade component or JavaScript module. If you reuse non-trivial custom code, retain the MIT attribution.
- Does alertify-bundle include tests or CI?
- The assessment states there is no evidence of test coverage, CI, or a changelog. That means behavior and compatibility are not validated by an automated pipeline you can inspect. If you reuse any code, you would need to add your own tests and documentation around it. Missing CI also increases the risk of stale dependencies and undocumented asset-publishing behavior.
- What are the alternatives to alertify-bundle for Laravel notifications?
- The closest alternative is integrating AlertifyJS directly with npm and Vite, which avoids the Symfony integration layer entirely. You can also evaluate Laravel-friendly notification or dialog libraries that fit Blade and Vite conventions. If you only need toasts, alerts, confirms, or prompts, a small custom wrapper around AlertifyJS is usually lower risk. The bundle is best treated as a reference, not a Laravel dependency.