Weave Code
Magic Starter Laravel Laravel Package
fluttersdk/magic-starter-laravel
fluttersdk/magic-starter-laravel is a Laravel starter kit that scaffolds a ready-to-use app with sensible defaults, authentication, and common tooling, so you can skip boilerplate and start building features faster.
Magic Framework Laravel backend starter package.
Frequently asked questions about Magic Starter Laravel
- How do I install fluttersdk/magic-starter-laravel in a new Laravel application?
- Install the package with Composer into a fresh Laravel project, then run the guided interactive setup wizard described in the README. The wizard is intended to wire configuration, assets, authentication screens, and the admin dashboard together. Review any published config and stub files after setup, and pin a specific package version for reproducible installs.
- Which Laravel versions are supported by magic-starter-laravel?
- The provided context does not list exact Laravel version constraints, so check the package composer.json and README before installing. Because the package is pre-1.0, verify compatibility in a fresh application and read the release notes before upgrading Laravel or the package. Do not assume support for every Laravel major version without confirming the current constraints.
- Is the included authentication flow ready for production use?
- The package includes pre-built login, registration, and password-reset screens, which gives you a substantial head start. Treat that scaffolding as a baseline and review mail settings, password-reset delivery, session and cookie configuration, and your application's security requirements. Production readiness still depends on your own hardening, configuration, and tests.
- Can I customize the admin dashboard and authentication screens?
- Yes, the admin dashboard layout is powered by Blade and Tailwind, and the package provides publishable config and stub files for customization. Publish the relevant assets and views, then edit them like normal Laravel application code. Keep your changes tracked so upgrades and future package releases are easier to review.
- Is the AI desk module in version 0.0.38 optional and safe to disable?
- The technical assessment explicitly questions whether the AI desk is genuinely inert when disabled, and it notes a prior defect where flag gating was not uniformly enforced. If you adopt 0.0.38 or later, review the configuration flags, avoid supplying provider credentials when the feature is unused, and test that no outbound calls occur in disabled mode. Do not assume optional means zero runtime surface without verification.
- What does the stored history summary persist, and how do I manage data retention?
- The release notes do not clearly state whether stored history summaries include user prompts, model responses, attachments, or only derived metadata. Review the migrations and package code before enabling the feature, then define retention periods, deletion paths, PII handling, and jurisdiction requirements for your application. Treat this as a data-governance decision, not just a configuration choice.
- How does cache token accounting affect AI quota limits in magic-starter-laravel?
- Version 0.0.38 now weighs cache tokens in AI quota accounting, so a given workload can consume more quota than it did under 0.0.37 or earlier. If you set limits or budgets against the older behaviour, recompute headroom and test representative workloads before relying on those numbers. This is a behavioural change that can appear as a silent cost or limit regression from the consumer side.
- Is fluttersdk/magic-starter-laravel stable enough for production?
- It is pre-1.0 software, and the jump from 0.0.33 to 0.0.38 introduces runtime AI features, new persistence, and changes in 0.0.34 through 0.0.37 that are not fully exposed in the provided release data. Pin a reviewed version, read release notes tag by tag, and consider vendoring or forking if you depend on it mainly as scaffolding. For production, weigh the single-maintainer risk and any ongoing data-governance obligations.
- How should I test a Laravel app scaffolded with Magic Starter?
- After installation, verify that the setup wizard completes, authentication screens work, password-reset mail is configured, and the admin dashboard renders correctly. Run your normal Laravel test suite and add coverage for customized routes, views, and configuration. If AI features are enabled, isolate provider credentials during tests and confirm that disabled mode makes no outbound calls.
- What are alternatives to magic-starter-laravel for Laravel scaffolding?
- Laravel Breeze and Jetstream are common starting points for authentication scaffolding, while Filament or Nova are options when you need a fuller admin panel. Magic Starter differentiates itself by bundling authentication, an admin dashboard, and publishable defaults in one guided installation. Compare maintenance expectations, customization needs, and AI or runtime footprint before choosing.
Weaver
How can I help you explore Laravel packages today?