Weave Code
Core Laravel Package
craftile/core
Craftile Core is the foundational Laravel/PHP package for the Craftile ecosystem, providing shared utilities, service provider wiring, configuration defaults, and common building blocks. Use it as the base dependency for Craftile-powered applications and extensions.
Craftile Core Package
Frequently asked questions about Core
- What is craftile/core and should I install it directly?
- Craftile Core is the foundational Laravel package for the Craftile ecosystem, providing shared contracts, service provider bootstrapping, configuration defaults, and reusable utilities. However, the craftile/core GitHub repository is a read-only subtree split, making it a distribution artifact rather than the supported install target. Install craftile/php instead and treat this repository as reference material only.
- How do I install Craftile Core in a Laravel application?
- Install the parent package with composer require craftile/php rather than requiring the craftile/core split directly. Laravel package auto-discovery registers the service provider, so no manual provider entry is needed. After that, publish the configuration file with the vendor publish command and adjust the options for your project. Check the monorepo README for the exact publish tag and any required setup steps, since documentation is thin.
- Which PHP and Laravel versions does craftile/core support?
- The repository materials do not publish a supported PHP and Laravel version matrix, and the package is pre-1.0 with thin documentation. Confirm the compatibility matrix against craftile/php, which is the supported install target, before building on it. Pin your Composer constraints and run a quick install test on your target Laravel version as an early validation step.
- Why is the craftile/core repository marked READ ONLY?
- It is an automatically generated subtree split of the Craftile monorepo, published so Composer can resolve the package name. All development, issues, and pull requests live in the parent repository, and the split has no independent release cadence or issue tracker. Because of that, bug fixes and security patches can lag behind the monorepo, so evaluate and track the parent package instead.
- Does Craftile Core support Laravel auto-discovery and config publishing?
- Yes. The package is built around standard Laravel conventions: a service provider foundation with sensible defaults, auto-discovery for zero-config installation, and a publishable config file for quick setup. That keeps adoption largely a configuration exercise rather than a paradigm shift. You should still review the published config, because the defaults may not match your admin requirements.
- Is craftile/core stable enough to use in production?
- It is pre-1.0 with thin documentation and an unproven semantic versioning record, so expect breaking changes in minor or even patch releases. It also has essentially no third-party adoption, meaning no community-vetted upgrade paths or Stack Overflow answers to lean on. For production, treat it as a bounded, timeboxed spike first and only commit after reading the changelog and pinning versions.
- What does Craftile Core actually do beyond scaffolding a Laravel admin panel?
- Core supplies the foundation for a declarative admin framework: you define resources against Eloquent models and it provides routing, forms, tables, validation, filtering, search, and policy-driven authorization. The intent is to replace hand-written Blade CRUD with configuration. Workflows, audit trails, large-scale localization, and digital asset management are build-on-top concerns rather than included features, so cost those gaps explicitly.
- How does authorization work in Craftile Core?
- Authorization is policy and gate driven, following standard Laravel conventions instead of bringing its own auth or permission system. Your existing policies, gates, and user provider stay in place, which keeps integration risk lower than a framework with its own auth layer. Review how resource-level permissions are enforced once you start declaring resources against your models.
- What are the alternatives to craftile/core for Laravel admin panels?
- The mature options are Filament, Laravel Nova, Backpack, and Orchid, plus hand-rolled Blade or Livewire CRUD. The practical difference is ecosystem depth: those packages have years of public usage, plugins, and answered questions, while Craftile currently has no visible third-party production footprint. Choose Craftile only if its resource-declaration model removes enough build time to offset that adoption risk.
- Who maintains craftile/core and what support is available?
- The package comes from a small or single-maintainer surface with no SLA, no support contract, and no visible security disclosure path. There is no issue tracker on the split repository, so all questions route to the craftile/php monorepo. Before committing, ask about release cadence, deprecation policy, license terms, and how security reports are handled.
Weaver
How can I help you explore Laravel packages today?