- How do I install jawira/skeleton with Composer?
- Install it as a dev dependency with composer require --dev jawira/skeleton, since it is a build-time tool rather than runtime code. Phing itself must be available on the machine or installed as a dev dependency, because the package only ships the build.xml and its targets. No service provider or configuration file is auto-registered, so nothing changes in your application bootstrap.
- Does jawira/skeleton work in a Laravel application?
- The package is framework agnostic: it is a set of Phing targets that run against any PHP repository, including Laravel. There is no Artisan bridge, service provider, or Laravel-specific configuration, so you invoke it with phing -f vendor/jawira/skeleton/build.xml instead of php artisan. Most targets duplicate what Laravel already provides through Artisan, Composer scripts, and CI pipelines, so evaluate whether you need a second build system.
- Which Laravel versions are supported by jawira/skeleton?
- There is no Laravel version constraint because the package does not depend on laravel/framework. Compatibility is determined by the PHP version that Phing and the targets can run on, not by your Laravel release. Treat it as version independent and test the targets against your own PHP and Phing versions before adopting them.
- How do I install PHPUnit using jawira/skeleton?
- Run phing -f vendor/jawira/skeleton/build.xml phpunit and the target scaffolds the PHPUnit setup files for the project. In a Laravel application there is usually already a phpunit.xml and a composer test script, so check whether the generated files conflict with your existing configuration. Review the diff before committing and prefer Laravel's own test runner if the outputs overlap.
- How do I generate a .gitignore file with jawira/skeleton?
- Run phing -f vendor/jawira/skeleton/build.xml gitignore, and add -Dforce=true if you want to overwrite an existing file. Remember that a Laravel project ships its own .gitignore containing framework-specific entries, so a forced overwrite replaces those customisations. Back up or diff the existing file first, then merge anything the target removes.
- Why did my build break after upgrading jawira/skeleton to 2.33.0?
- Version 2.33.0 renamed the analysis targets to check targets, so any build.xml, Composer script, or CI job calling the old target names will fail. The rename shipped on a minor version bump, which means a caret constraint like ^2.33 would absorb it silently. Audit every invocation of the package, replace analysis with check, and pin an exact version if you need stability.
- What does the new check outdated dependencies target do?
- It is a narrower, faster target that inspects outdated packages without running the full check suite, added in the 2.33.0 release. It effectively duplicates composer outdated --direct, and security auditing is already covered by composer audit. In a Laravel project you can run the native Composer commands with zero extra dependency surface.
- Can I use jawira/skeleton in CI or production deployments?
- Use it as a dev-time build tool in local and CI environments only, installed with require-dev so it never reaches production. Adding Phing plus this package to containerised or serverless Laravel deployments increases image size and deployment complexity for tasks your pipeline already handles. GitHub Actions, GitLab CI, Composer scripts, and tools like Deployer or Envoyer cover the same ground natively.
- Is jawira/skeleton actively maintained and safe to depend on?
- The repository is not abandoned: recent merged pull requests and tagged releases show ongoing activity under the MIT license. However, it has a single maintainer, very low adoption, and has already shipped a breaking target rename on a minor release, so there are no security audits and no deprecation shims. Pin exact versions, avoid caret ranges, and re-validate manually on each upgrade.
- What are the alternatives to jawira/skeleton for Laravel build automation?
- Use Composer scripts and Artisan commands for task running, PHPUnit or Pest for tests, Laravel Pint for linting, and GitHub Actions or GitLab CI for pipelines. Git hooks can be handled by CaptainHook or GrumPHP, and deployments by Deployer, Envoyer, or Forge. These are standard in the Laravel ecosystem, require no additional Phing dependency, and avoid the tooling fragmentation this package introduces.