Weave Code
Invytr Laravel Package
glaivepro/invytr
Invytr is a Laravel package for invitation-based registration. It lets you generate and manage invite codes, restrict signups, and track invitations, with configurable expiration and usage limits for controlled onboarding.
Laravel package for giving admin-created accounts to users via 'set-password' email.
Frequently asked questions about Invytr
- How do I install glaivepro/invytr in a Laravel application?
- Install it with Composer using composer require glaivepro/invytr, then check the repository README for any required service provider registration or publishing steps. Laravel package auto-discovery may handle the provider, but verify that for your Laravel version. Run any migrations and publish the config if the documentation calls for it. Test the install in a scratch branch before adding it to a production dependency set.
- Does Invytr support Laravel 11 and Laravel 12?
- Release v1.0.11 is noted as adding Laravel 11 and Laravel 12 support alongside PHP 8.3 and 8.4. That release note is the only evidence available here, so confirm the actual constraints in composer.json with composer why-not glaivepro/invytr ^1.0. Also check whether a CI matrix actually exercises these Laravel and PHP combinations rather than relying on a declared support claim.
- What PHP versions does glaivepro/invytr require?
- The v1.0.11 release note states PHP 8.3 and PHP 8.4 support. Whether earlier PHP versions remain supported is not stated in the available information. Verify the require.php constraint in composer.json before committing to the package. Declared support is not the same as tested support, so check CI if it exists.
- Does Invytr still support Laravel 10?
- The release note does not say whether v1.0.11 retains Laravel 10 or raises the minimum to Laravel 11. That distinction matters: if Laravel 10 was dropped, projects still on Laravel 10 are stranded at v1.0.10 and will not receive future fixes. Check the changelog and the composer.json constraints to confirm. Treat this as a blocking question before adoption if you still run Laravel 10.
- How do Invytr set-password invitation emails work?
- Invytr is described as giving admin-created accounts to users through a set-password email, so an administrator creates the account and the user receives a link to choose their own password. The exact routes, token handling, and mail templates are not documented in the material available here. Read the README and source to confirm how tokens are generated, stored, and expired. Test the full flow end to end before relying on it in production.
- Can I configure invitation expiration and usage limits in Invytr?
- The package blurb mentions configurable expiration and usage limits for controlled onboarding. The specific configuration keys and defaults are not included in the available information. Publish the package config and read the file to see the actual options and their defaults. Confirm whether limits apply per invite code, per user, or globally before designing your onboarding rules around them.
- Does Invytr publish config files or migrations?
- It is not confirmed whether Invytr publishes config files or migrations; the available assessment explicitly flags this as an open question. Published config and migrations become your code and your upgrade burden, so check before installing. Look for a service provider with publishes() calls, or run vendor:publish and inspect what appears. Decide deliberately whether to publish artifacts or keep the package defaults.
- Is glaivepro/invytr safe to use in production?
- The package is at v1.0.11, which is young and pre-2.0, so semver permits the maintainer to ship breaking changes in minor releases. There is no stated security disclosure policy or support window in the available information, and the documentation is thin. Treat that documentation thinness as a risk in its own right. Pin to ^1.0, review the changelog on every update, and keep a rollback plan.
- How should I test Invytr invitation and set-password flows?
- Test the invitation and set-password flow end to end in a disposable branch using your real dependency set. Use Mail::fake() to assert the set-password email is sent, and inspect the generated link. Cover expiration, reuse, and usage-limit paths explicitly rather than only the happy path. Confirm behavior on your actual Laravel and PHP versions instead of trusting declared support.
- What are alternatives to Invytr for Laravel invitation-based registration?
- Laravel has no first-party invitation package, so alternatives include building a small invite table with middleware yourself or evaluating other community invitation packages. The information available about Invytr is thin, so compare candidates on maintenance activity, Laravel 12 support, and test coverage. Check Packagist and GitHub for release cadence and open issues before choosing. Prefer a package whose constraints resolve cleanly against your existing lock file.
Weaver
How can I help you explore Laravel packages today?