- Does jeremykenedy/slack-laravel support Laravel 9, 10, or 11?
- No. The last release is v2.6.0 from October 2020, which was the Laravel 8 compatibility release targeting PHP 7.3+, so the illuminate/* constraints will most likely block Composer resolution on Laravel 9 and newer. Run composer why-not jeremykenedy/slack-laravel against your actual stack before planning any work around it, because a failed resolve turns this into a fork-or-replace decision rather than a cheap dependency. There has been no release in roughly five years, so there is no upstream to wait for.
- How do I install and configure jeremykenedy/slack-laravel?
- Install it with Composer; on Laravel 8 the service provider and Slack facade are auto-discovered, so no manual registration is needed. Publish the package config with php artisan vendor:publish, then set your Slack incoming webhook URL in your .env file. Onboarding on the supported matrix is typically sub-day for one engineer. Verify the endpoint resolves in config after you run config:cache.
- What is the difference between this package and Laravel's built-in Slack notifications?
- Laravel ships a native Slack notification channel using Notification::route('slack', ...) plus SlackMessage, which covers comparable outbound messaging with zero third-party surface. This package adds a facade, a publishable config file, and channel helpers, but the underlying capability is essentially a single HTTP POST to a webhook. If the framework-native channel is viable on your target stack, the incremental value of this dependency is low.
- Can it send messages through both incoming webhooks and the Slack Web API?
- Yes. The package wraps an outbound HTTP POST to a Slack incoming webhook and also exposes helpers for the Slack Web API, driven by a .env-configured endpoint. Architecturally it is a thin, replaceable adapter at the edge of your domain rather than a deep integration layer. Treat it as a commodity dependency you contain, not a platform component you build on.
- Can I route Laravel logs to a Slack channel with this package?
- Yes, the package advertises routing logs to Slack channels through its configurable wrapper, so you can add Slack as a logging destination. Be aware that webhooks are fire-and-forget, so an unreliable notifier can become a single point of failure for alerting. For anything you depend on being delivered, add your own retry and dead-letter path around it.
- Does jeremykenedy/slack-laravel support queueing, retries, or Slack rate limits?
- No. Webhook delivery is fire-and-forget with no retries, no backoff, no rate-limit awareness, and no dead-letter path. Slack throttles roughly one message per second per channel, and a 2020 wrapper does not track that behavior. If you need durability, wrap calls in a queued job with your own retry and backoff policy rather than relying on the package.
- How does the package report failed Slack requests?
- It depends on how the wrapper handles responses, so verify it against your version: failures may surface as an exception, a silent boolean, or nothing at all. There is no telemetry hook, so you should assert on non-2xx responses yourself and record failures in your existing monitoring. Alerting built on an unverified notifier is a classic single point of failure, so confirm the failure mode in a staging channel before go-live.
- How do I test Slack notifications without posting to a real channel?
- The package does not document a built-in fake, so test the boundary instead by faking the HTTP client with Http::fake, or by putting a small notifier interface in front of it and swapping in a fake implementation. Assert that your code builds the expected payload and channel, not that Slack accepted it. Reserve one manual smoke test per environment for the real webhook.
- Where should I store the Slack webhook URL, and does it survive config:cache?
- The webhook URL is a bearer credential in practice, so anyone holding it can post to the channel: keep it in your secret store or .env, never in version control. Plan for rotation, redaction from logs and exception handlers, and channel mapping and revocation ownership. Confirm the value is read through config, which survives php artisan config:cache, rather than through direct env() calls that return null once config is cached.
- Is jeremykenedy/slack-laravel still maintained and safe for production?
- It has 54 stars, a single maintainer, and no release since October 2020, with no visible CI matrix or security-response process. The MIT license is the mitigation: forking or replacing it is cheap, and the capability being abstracted is only a few dozen lines of an HTTP POST. It also predates Slack's move to Block Kit, so legacy attachments payloads and future API drift are your problem, not the vendor's. On Laravel 8 it is not your blocker, but it is another line on the upgrade ledger.