- What is jonpurvis/squeaky used for?
- Squeaky is a Laravel validation rule designed to help catch profanity in user input. You can use it in form requests or validators to reject offensive language in fields such as comments, usernames, or reviews. It is focused on validation rather than CSS or Blade cleanup.
- How do I install jonpurvis/squeaky in a Laravel application?
- Install it with Composer using composer require jonpurvis/squeaky, then reference the rule in your Laravel validation logic as described in the README. Because v3.3.0 is a compatibility-boundary release, confirm the exact Laravel and PHP constraints in the package composer.json before upgrading. If your tests use PestPHP, check whether your test stack can move to PestPHP 5.
- Which Laravel versions does Squeaky support?
- The v3.3.0 release drops Laravel 10 and 11 support, so it likely requires Laravel 12 or newer, but you should verify the exact constraint in composer.json. Earlier releases such as v2.4.0 may remain the practical option for Laravel 10 and 11 applications. Do not assume v3.3.0 works on older Laravel versions without checking.
- Does jonpurvis/squeaky work with Laravel 10 or 11?
- Squeaky v3.3.0 does not support Laravel 10 or 11 according to the release assessment. If your application remains on Laravel 10 or 11, v3.3.0 is not a viable standalone upgrade. A v2.4.0 fallback may exist, but confirm its maintenance and security posture before relying on it.
- Is Squeaky a runtime dependency or a dev-only package?
- Squeaky is a Laravel validation rule, so if it validates production form input, treat it as a runtime dependency. If you only use it in development or CI checks, runtime architecture impact is lower. Confirm your actual usage before scheduling the v3.3.0 upgrade.
- What changed in Squeaky v3.3.0?
- The v3.3.0 release is described as a compatibility-boundary release rather than a feature release. It adds PestPHP 5 support and drops Laravel 10 and 11 support. The release note is sparse and compares v2.4.0 to v3.3.0, so review the full changelog and Composer constraints for hidden breaking changes.
- Can I use Squeaky with PestPHP 5?
- Squeaky v3.3.0 adds PestPHP 5 support, which primarily affects the package test suite and CI compatibility. It does not necessarily change how the validation rule works in production. Verify that your team's Pest plugins and test APIs are compatible with PestPHP 5 before upgrading.
- How should I test profanity validation with Squeaky?
- Write Laravel validation tests that assert input containing a blocked word fails and clean input passes. If you use PestPHP 5, run the tests through your normal CI matrix after upgrading. Also verify the rule's behavior with the exact profanity list and validation messages configured in your app.
- Are there alternatives to Squeaky for profanity filtering in Laravel?
- You can build a custom Laravel validation rule around your own word list, use regex or string matching, or evaluate a third-party profanity filter package. Squeaky's advantage is that it provides a Laravel validation rule for this specific purpose. Compare maintenance activity, Laravel version support, and false-positive behavior before choosing.
- How do I upgrade Squeaky from v2.4.0 to v3.3.0 safely?
- First confirm your application is on the Laravel baseline required by v3.3.0 and that your test stack can use PestPHP 5. Upgrade Laravel or PHP first if needed, then update the package in a dedicated branch, commit the lockfile, and run the full test suite. For Laravel 10 or 11 applications, stay on v2.4.0 or treat the package upgrade as part of a larger platform upgrade with a documented rollback plan.