- Can I install nunomaduro/laravel-meetups in Laravel 11?
- Probably not cleanly. The package dates to a June 2017 release and targets Laravel 5.4/5.5-era conventions and PHP 7.x, so Composer will likely block installation on Laravel 10-12 and PHP 8.2+ without --ignore-platform-reqs. Even with that flag, the code is a console command rather than a supported library integration. For a current app, copy or rewrite the command instead of depending on the package.
- Does laravel-meetups include a service provider, facade, or Blade helpers?
- The repository does not show a service provider, facade, config-driven view layer, or driver abstraction. Despite descriptions mentioning a fluent API and Blade-ready data, the code is essentially an Artisan command that fetches meetups and prints them. Treat those claims as aspirational or documenting an unmerged branch, not as package features. You would need to build the presentation layer yourself.
- Is nunomaduro/laravel-meetups still maintained?
- No active maintenance is evident. It has roughly 10 stars, zero dependents, and no release since 2017, with no security or compatibility updates. That makes it high risk as a dependency for a modern Laravel application. Use it only as a reading reference or a starting point for your own command.
- What data source does laravel-meetups use for meetup listings?
- The original code appears to fetch meetup data from an external API, most likely the Meetup.com API of that era. Meetup.com's commercial and technical terms have changed substantially since 2017, so the fetch layer is probably dead regardless of PHP version. Confirm that your intended data source is still accessible under current terms before writing any code.
- How can I show local Laravel meetups in a Laravel application?
- For a new feature, do not adopt this package as-is. Build a small command or service that calls a current meetup data source, stores normalized results, and exposes them to Blade or Inertia. Use Laravel's Http facade for retries and Http::fake() in tests, put locations and API credentials in config/meetups.php and env vars, and cache results with Cache::remember. This is typically about 100-150 lines and gives you full ownership.
- Can I filter meetups by city or country with laravel-meetups?
- The package description promises filtering by city or country, but the repository does not demonstrate a queryable service or API for that. It is a console application that prints fetched meetups, so filtering is not a supported library feature. If you need location filtering, implement it in your own data model or query layer after normalizing the source data.
- How should I cache meetup data in Laravel?
- Use Cache::remember with a TTL aligned to event cadence, such as a few hours to a day, rather than caching indefinitely. Cache the normalized list after the HTTP fetch, not raw responses, so your views stay simple. Add a manual refresh command and a scheduler entry, and return a meaningful exit code so monitoring can detect failures.
- Are there tests I can rely on in laravel-meetups?
- No meaningful test suite is available to rely on. The original package offers no tests that validate the fetch layer or command behavior against current Laravel. If you fork or copy the code, backfill tests using Http::fake() and command tests that assert output and exit codes. Treat the absence of tests as a reason to rewrite rather than vendor.
- What are alternatives to nunomaduro/laravel-meetups?
- There is no drop-in maintained Laravel meetup directory package identified here. The practical alternative is a small in-house command plus a current events API or curated data source, with caching and scheduling built on Laravel's native features. If you only need a static events page, a config file or database table may be simpler than any package.
- How do I schedule a meetup refresh command in Laravel?
- Write a command that fetches and normalizes meetups, then register it in routes/console.php or your scheduler with a frequency that matches event updates. Use Laravel's Http facade with timeouts and retries, and cache the result so scheduled runs do not hammer the upstream source. Add structured output and a non-zero exit code on failure so your scheduler monitoring can alert you.