Weave Code
Poke Laravel Package
laragear/poke
Laragear Poke is a small Laravel utility for poking your application: dispatch a quick signal, run a lightweight task, or confirm a service is alive using a clean, fluent API with minimal setup and no configuration. It fits neatly into Laravel's ecosystem, so pokes can run in tests, scheduled jobs,...
Keep your forms alive, avoid TokenMismatchException by gently poking your Laravel app.
Frequently asked questions about Poke
- What is Laragear Poke used for in Laravel?
- Laragear Poke is a small Laravel utility for keeping forms alive and avoiding TokenMismatchException by gently poking your application. It lets you dispatch a quick signal, run a lightweight task, or confirm that a service is alive through a fluent API. It requires minimal setup and no configuration, and it can run in tests, scheduled jobs, or on demand.
- How do I install Laragear Poke with Composer?
- Install it with composer require laragear/poke in a Laravel application. The package follows standard Laravel package conventions, so installation is normally Composer plus optional publishing of config or assets. You do not need configuration to get started, but you should check the composer.json constraints for PHP, Laravel, Livewire, and Filament compatibility before installing in an existing project.
- Does Laragear Poke support Laravel 10 and Laravel 11?
- Laragear Poke is Laravel-native and is designed to fit Laravel's service provider, configuration, and facade conventions. The package is commonly evaluated for Laravel 10 and Laravel 11 applications, but you should confirm the exact Laravel and PHP constraints in the package's composer.json for your chosen version. If you use the Livewire or Filament helpers, also verify that your Livewire 3 and Filament 3 versions match the package's peer dependencies.
- What do the Livewire and Filament helpers in Laragear Poke v5.1.0 do?
- Version 5.1.0 adds Livewire and Filament helpers that reduce custom glue code for teams using Livewire 3 and Filament 3. They likely provide traits, components, Filament actions, or widgets that integrate poke behavior into interactive UI and admin panels. Treat them as optional integrations and validate registration, publishing, and version compatibility in a non-production environment before relying on them.
- Do I need to publish configuration or assets for Laragear Poke?
- The core package emphasizes minimal setup and no configuration, so basic use should work without publishing anything. Optional config or asset publishing may be available, and the Livewire or Filament helpers could require additional registration or panel setup. Document any publish and registration steps during your spike so future upgrades remain reproducible.
- How does Laragear Poke help avoid TokenMismatchException?
- Poke is intended to keep long-lived forms alive by gently poking the Laravel application before the session or CSRF token expires. That reduces the chance of users submitting a stale form and hitting TokenMismatchException. You integrate the poke call into your frontend or application flow using the package's fluent API, then test it against your session and CSRF settings.
- Can I run Laragear Poke in tests and scheduled jobs?
- Yes. The package is described as usable in tests, scheduled jobs, or on demand, not only from browser forms. That makes it suitable for lightweight liveness checks or quick signals inside Laravel's scheduler and test suite. Keep these calls small and assert expected behavior in your own test matrix.
- Is Laragear Poke safe to use in production?
- The core package is lightweight and Laravel-native, so production risk is generally low, but you should review any routes, actions, or authorization introduced by the Livewire and Filament helpers. The package has a single maintainer and a niche footprint, so pin to a compatible version such as ^5.1 and monitor GitHub activity. Test graceful degradation when Livewire or Filament is absent and check the blast radius if a helper component throws in an admin panel.
- What are alternatives to Laragear Poke for keeping Laravel forms alive?
- Alternatives include tuning Laravel's session lifetime and CSRF behavior, adding a small custom keep-alive endpoint, or using your own Livewire polling logic. Laragear Poke's value is its fluent, Laravel-native poke API with minimal setup and optional Livewire 3 and Filament 3 helpers. Evaluate those built-in options against your exact form lifetime and admin panel requirements before adding a dependency.
- How is Laragear Poke maintained and what happens if it stalls?
- The package is maintained by a single maintainer with community support through GitHub issues, so release cadence and responsiveness should be monitored. For a production integration, pin to ^5.1, review the changelog on upgrades, and keep internal capability to debug or fork the package. If the package stalls, be prepared to replace it with a small internal poke endpoint or an alternative keep-alive approach.
Weaver
How can I help you explore Laravel packages today?