Weave Code
Fastapi Laravel Package
larafast/fastapi
A Laravel package for quickly scaffolding API endpoints and resources, reducing boilerplate so you can build JSON APIs faster with familiar Laravel conventions and tooling.
A Fast Laravel package to help you generate CRUD API Controllers and Resources, Model.. etc
Frequently asked questions about Fastapi
- How do I install larafast/fastapi in a Laravel project?
- Install it with Composer, ideally as a dev dependency using composer require larafast/fastapi --dev, then publish any config or stubs the package provides. After that you run the package's Artisan generator command to scaffold a model, CRUD API controller, and API resource. Always check the repository README for the exact command name and publish tags, because the package is not actively maintained.
- Which Laravel and PHP versions does larafast/fastapi support?
- The last release was March 2023, so it most likely targets Laravel 9 and possibly early Laravel 10 rather than Laravel 11 or 12. You should inspect the composer.json Illuminate and PHP constraints before installing, because Composer may block installation on newer Laravel versions without ignore-platform-reqs or a fork. Running it on an unsupported Laravel major means you own compatibility testing and any needed patches.
- What files does larafast/fastapi actually generate?
- The package is a dev-time Artisan code generator that scaffolds models, CRUD API controllers, and API resources into your application source tree. It may also emit related files such as routes, migrations, or factories, but you must confirm that against the README or a test run. It has no runtime footprint because the generated output is plain PHP committed to your repository.
- Does larafast/fastapi generate FormRequests, policies, and tests?
- There is no evidence that it generates FormRequests, authorization policies, or automated tests, and the evaluation flags this as a key unknown. Generated CRUD controllers are exactly where validation, authorization, and mass-assignment protections are often skipped. Treat the output as a starting point and manually add FormRequests, policies or gates, pagination, filtering, and feature tests before merging.
- Is larafast/fastapi safe to use in production?
- It has no runtime footprint, so production risk comes from the generated code and from dependency provenance, not from a service running in your app. The package is effectively unmaintained with a single maintainer, zero dependents, and no visible security disclosure process. Only use it as a require-dev convenience on a codebase where you review every generated controller for validation, authorization, and mass-assignment safety.
- Can I customize the stubs used by larafast/fastapi?
- The evaluation lists stub publishability and customization as an open question, so verify whether vendor:publish exposes the stubs before adopting it. If stubs are publishable, you can encode team conventions such as FormRequests, policies, and pagination defaults. If they are not, you are accepting the package's templates as-is, which makes an internal generator or a fork the better long-term option.
- Is larafast/fastapi still maintained?
- No meaningful maintenance is visible: the last release was March 2023, with no signal across the Laravel 10, 11, or 12 cycles. It has one maintainer, no governance, no security disclosure process, and no evidence of production use. Adopting it means your team effectively owns the templates and must validate them on every Laravel major upgrade.
- How does larafast/fastapi compare to make:model -mcr and make:resource?
- Native Laravel commands already generate a model with migration and controller, and make:resource creates API resources, so the package's advantage is bundling CRUD controller and resource scaffolding into one step. The evaluation recommends measuring endpoints per hour against native generators including review and cleanup time, not just generation time. For most teams with an existing convention, Blueprint, InfyOm, Apiato, or a small internal Artisan command will be a better fit.
- How do I remove larafast/fastapi if I stop using it?
- Because the generated files are committed source and the package has no runtime footprint, removal is a simple composer remove larafast/fastapi with no data or runtime migration. The real residual cost is auditing code that was already generated against your current standards. This cheap-to-try, cheap-to-abandon exit story is the package's strongest argument.
- What is the best way to evaluate larafast/fastapi before adopting it?
- Run a one to two day spike in a scratch branch on your target Laravel version, generate one representative endpoint, and diff it against a hand-written reference endpoint. Compare validation, authorization, pagination, filtering, error handling, and test coverage, and measure endpoints per hour including review and cleanup. Then decide whether to adopt with customized stubs, fork and own it, or harvest the stubs as reference for an internal generator.
Weaver
How can I help you explore Laravel packages today?