Larascord Laravel Package

Product Decisions This Supports

• Authentication roadmap: Confirms Discord as a viable social-login provider, letting us prioritize "sign in with Discord" for community/gaming-oriented audiences without committing to custom OAuth work.
• Framework upgrade sequencing: v8.0.0 adds Laravel 13 support, so our Laravel 13 upgrade plan can keep this dependency rather than fork or replace it — a direct input to upgrade timing and scope.
• Build vs. buy: Reinforces the default of buying the integration (composer dependency) over building and maintaining Discord OAuth flows in-house. Only worth revisiting if we need behavior beyond login (roles/guild sync, bot actions), which this package doesn't cover.
• Migration budgeting: The v8 major version ("redesign architecture for existing project compatibility") is a breaking change. If we are already on v7, we must budget engineering time for migration and regression testing on the auth path — or deliberately pin v7 and accept missing Laravel 13 support.
• Release-cadence risk input: Two consecutive majors (v7 → v8), a single-maintainer project, and architecture churn are signals to include this dependency in our upgrade-risk and bus-factor reviews.

When to Consider This Package

• Our product is Laravel-based, targets a Discord-centric or gaming/community audience, and needs a low-effort "Login with Discord" flow.
• We want OAuth handled by a maintained package rather than hand-rolled token exchange, state handling, and user mapping.
• We are planning or already on Laravel 13 and need a compatible auth provider — v8 is the version to evaluate.
• We are fine pinning a major version and absorbing occasional breaking releases with a migration ticket.

Look elsewhere when:

• Discord is not a primary audience channel — Laravel Socialite plus an official provider covers multiple OAuth providers with less single-vendor risk.
• We need enterprise identity (SAML, SCIM, OIDC with strict compliance) — this is consumer social login, not workforce SSO.
• We need deep Discord integration (guild/role sync, bot permissions, webhooks) — this package is authentication-focused, and we'd be stretching it past its scope.
• We require vendor SLAs or multi-maintainer support — this is a small, single-maintainer open-source project, so plan for the possibility of slow fixes or a future fork/replacement.
• We are on v7 and cannot absorb a breaking change this cycle — pin v7, defer v8 migration, and accept that Laravel 13 upgrades are blocked until we move.

How to Pitch It (Stakeholders)

For executives: Discord login removes signup friction for our target community and is a commodity integration — we should buy it, not build it. The good news is the new v8 release supports Laravel 13, so it does not block our platform upgrade. The caveat is that v8 is a breaking release from a small open-source project, so adopting it means a one-time migration ticket and ongoing diligence on version pinning. Net: low cost, real conversion upside, manageable dependency risk.

For engineering: v8.0.0 is a major release with two changes that matter: Laravel 13 compatibility, and an architecture redesign aimed at existing-project compatibility. Treat it as breaking: review the changelog and upgrade guide, run the auth flow end-to-end (redirect, callback, user creation/mapping, token refresh) in staging, and pin the exact version in composer.json. If we're mid-upgrade cycle, sequence this alongside — not on top of — the Laravel 13 jump. Since the project is single-maintainer, avoid forking; if we need custom behavior, wrap the package behind our own auth interface so it can be swapped for Socialite or a fork with minimal blast radius.