Weave Code
Laravel Waitlist Laravel Package
offload-project/laravel-waitlist
Laravel Waitlist makes it easy to add waitlist signups to your app. Collect emails, manage entries, and control access with invite or referral codes. Configurable models, notifications, and events help you launch and grow your product.
A simple and elegant waitlist package for Laravel applications
Frequently asked questions about Laravel Waitlist
- How do I install offload-project/laravel-waitlist in a Laravel application?
- Install it with Composer using composer require offload-project/laravel-waitlist. The package uses Laravel package auto-discovery, so its service provider is registered automatically. Publish the config and migrations, then run php artisan migrate. If you do not want the package's default routes or views, disable them in config and point your own controller at the package model or action.
- Which Laravel and PHP versions does laravel-waitlist support?
- Check the require and require-dev blocks in the package composer.json, since that constraint file is the authoritative support matrix. Also look for a CI workflow in the repository that runs the test suite against each Laravel major, which is the best proof that the advertised versions actually work. Because Laravel ships a major annually, verify the constraint before planning an upgrade rather than assuming compatibility.
- Can I use laravel-waitlist with Livewire, Inertia, or a headless JSON API?
- Yes, the package is front-end agnostic in principle. The lowest-friction path is to disable the auto-registered routes and write a thin controller that validates the request and calls the package's model or signup action. That lets you return an Inertia response, a Livewire component update, or JSON without fighting an opinionated Blade form.
- How do I customize the waitlist model or database table?
- The package advertises configurable models and publishable migrations, so you can swap in your own model class and adjust the schema after publishing. Keep the package's table as a separate bounded table rather than modifying your users table. If you change the model, make sure it still implements whatever contract or traits the package expects for signups and notifications.
- How do invite codes and referral codes work in laravel-waitlist?
- The package supports controlling access with invite or referral codes, which lets you gate signups or attribute new entries to an existing participant. Referral handling usually means storing the referring code alongside the signup so you can report on it later. Confirm the exact storage columns and validation rules in the published migration and config before building reporting or rewards on top.
- Are waitlist confirmation emails queued or sent inline during the request?
- This depends on how the package registers its notifications and whether they implement ShouldQueue. Check the notification classes and the mail configuration after publishing; if they send inline, implement ShouldQueue on your own notification or override the config to avoid slow signup responses and deliverability problems. Queued mail also requires a running worker in production.
- Does laravel-waitlist emit events so I can sync signups to analytics or a CRM?
- The package advertises events as part of its feature set, which is the right integration point for analytics, CRM sync, or internal notifications. Listen for the signup event in your own EventServiceProvider rather than forking the package. Verify the exact event class name and payload in the source before wiring listeners.
- Is it safe to expose an unauthenticated waitlist signup endpoint in production?
- A public signup form is a spam and compliance target, and a simple package usually does not include bot mitigation, rate limiting, or consent capture out of the box. Add Laravel's rate limiter middleware, a honeypot or CAPTCHA, and explicit consent language, and define a deletion and export process for GDPR requests. Treat the endpoint as PII-handling infrastructure even though it only collects an email.
- Does laravel-waitlist handle double opt-in and duplicate email signups?
- Verify this in the source before relying on it. Many simple waitlist packages enforce a unique email constraint and may reject duplicates silently, but double opt-in with a verification token is a product decision that often needs custom work. If you need confirmed-only entries, add a verification column and a signed route rather than assuming the package covers it.
- Is laravel-waitlist actively maintained, and what are the alternatives?
- The repository has a modest adoption signal, around 57 stars, which suggests few production users and limited community coverage. The MIT license protects you legally if the maintainer walks away, but the operational risk of a single-maintainer package remains. Before adopting it, review recent commit activity, open issues, and test coverage, and keep an exit plan such as a thin custom controller over your own waitlist table.
Weaver
How can I help you explore Laravel packages today?