Weave Code
HiDev plugin for Scrutinizer CI
Frequently asked questions about Hidev Scrutinizer
- Is hiqdev/hidev-scrutinizer compatible with Laravel 10+ or PHP 8.2+?
- No, this package was last updated in 2017 and only supports PHP 5.6–7.x. Laravel 10+ requires PHP 8.2+, so it won’t work without major compatibility fixes. Avoid unless you’re using an unsupported Laravel/PHP version.
- Do I need HiDev for this package, and is it worth adopting just for Scrutinizer CI?
- Yes, HiDev is a mandatory dependency, and it’s a niche tool not widely used in Laravel projects. Only adopt this if HiDev is already part of your stack—otherwise, it adds unnecessary complexity with no Laravel-native benefits.
- Can I use this package with GitHub Actions or GitLab CI instead of Scrutinizer CI?
- No, this plugin is *only* for Scrutinizer CI. If your team uses GitHub Actions, GitLab CI, or other modern CI tools, this package provides zero value. Scrutinizer CI is rarely the default choice for Laravel projects today.
- How do I install and configure this package in a Laravel project?
- Run `composer require hiqdev/hidev-scrutinizer`, then configure HiDev to use the plugin (check HiDev’s docs). There’s no Laravel service provider or Facade—setup is manual. Ensure `.scrutinizer.yml` exists and Scrutinizer CI is already configured.
- Will this package work with PHPUnit + Xdebug or PestPHP for coverage?
- It supports coverage uploads via Scrutinizer’s Ocular, but Laravel’s ecosystem typically uses PHPUnit + Xdebug or PestPHP. If your team relies on these tools, this plugin may not integrate seamlessly and could introduce extra steps.
- Are there modern alternatives to Scrutinizer CI for Laravel projects?
- Yes. Laravel projects commonly use GitHub Actions, GitLab CI, or Laravel Forge for CI/CD. These tools offer better Laravel integration, native support for PHP 8.x, and no HiDev dependency. Scrutinizer CI is outdated for most use cases.
- How do I verify if this package is still maintained or safe to use?
- The last release was in 2017, and there’s no recent activity. Given Laravel’s rapid evolution, this package poses high compatibility risks. If maintenance is critical, avoid it unless you’re willing to patch it yourself.
- Does this package support Laravel’s native testing tools like Dusk or Pest?
- No, it’s designed for Scrutinizer CI’s Ocular coverage tooling, which doesn’t natively integrate with Laravel’s testing ecosystem (Dusk, Pest, or PHPUnit). You’d need to manually bridge coverage reports, adding complexity.
- What happens if I upgrade Laravel or PHP, and this package breaks?
- You’ll likely face compatibility issues since it’s untested on PHP 8.x or Laravel 9+. Without active maintenance, fixes won’t come from the package authors. Plan for manual patches or seek alternatives if upgrading.
- Can I use this package in production without HiDev’s other features?
- No, HiDev is a full dependency, not a plugin. If you only need Scrutinizer CI integration, this package forces you to adopt HiDev’s entire toolchain, which may include unwanted features like code generation or automation.
Weaver
How can I help you explore Laravel packages today?