- What is goodm4ven/anvil used for in Laravel?
- Anvil is described as a Laravel/PHP foundation for reusable application features and package development, with service provider integration, configuration, stubs, and test-friendly structure. The technical assessment frames it as an internal toolkit for authoring Laravel packages rather than a general runtime library. Audit its source before adopting because public documentation is absent.
- Is Anvil a runtime package or a dev-only package scaffold?
- It is best treated as a dev-only scaffold or template for package repositories, not as production application runtime code. The assessment says it belongs in require-dev or as a scaffold/template. Confirm whether its service providers and config are dev-only by auditing composer.json and the source.
- How do I install goodm4ven/anvil with Composer in Laravel?
- Composer installation is mechanically simple, but the assessment recommends not requiring the archived upstream directly. Audit and vendor the source, then fork it under your organization and install through a private Composer VCS or path repository with a pinned tag. For evaluation only, install it in a throwaway Laravel app.
- Which Laravel and PHP versions does Anvil support?
- The provided context does not state exact Laravel or PHP version ranges. The repository guidelines reference PHP 8.3 with strict typing, but that is a development-culture signal, not a compatibility guarantee. Check composer.json constraints and run a compatibility spike against your supported Laravel version matrix.
- Is it safe to use an archived Composer package in production?
- The technical risk is high because the package is archived, with no security patches, no Laravel major-version compatibility work, and no upstream issue triage. It has zero stars and no dependents, so there is little community validation. Do not use it in production without a source audit, fork, pinned version, and clear internal ownership.
- Does Anvil register service providers or publish config files?
- The overview says it has Laravel-native service provider and configuration integration, and the assessment asks what it registers and publishes. It may include service providers, config publishing, Artisan commands, stubs, or test harness pieces, but the excerpt does not itemize them. Audit the source and composer.json to confirm auto-discovery and whether anything leaks into runtime.
- Can I use Anvil for a single Laravel application instead of package development?
- For a single Laravel application, the value proposition is largely irrelevant according to the assessment. It is intended for teams standardizing first-party package development across repositories. If you only need application features, use Laravel conventions or extract only useful stubs and defaults.
- How should I test Anvil inside a Laravel app?
- Test it inside a throwaway Laravel application and run its own tests if present. Check service-provider auto-discovery, config publishing, Artisan commands, and dependency constraints in isolation. Treat every Laravel upgrade as a fork-maintenance event once you adopt it.
- What are alternatives to Anvil for Laravel package scaffolding?
- Alternatives include Laravel's own package skeleton and discovery, Pest or PHPUnit scaffolding, and your organization's existing package template. The assessment asks whether Anvil duplicates existing package skeleton capability. Prefer maintained, documented scaffolding unless Anvil's conventions provide clear multi-package value.
- How do I maintain a fork of Anvil after the upstream is archived?
- Fork the MIT-licensed source into an internal Git repository, pin a tag, and publish via a private Composer VCS or path repository. Budget recurring effort for each Laravel major release and PHP minor that changes typing or deprecations. Pilot in one non-critical package repository and document conventions before expanding.