Weave Code
Framework Laravel Package
laravel/framework
Laravel Framework core provides an elegant PHP foundation for building web apps: fast routing, powerful service container, sessions/caching, database migrations, queues, and real-time broadcasting—tools that scale from small projects to large applications.
Laravel is a web application framework with expressive, elegant syntax.
Frequently asked questions about Framework
- What’s the latest Laravel version and its PHP version requirement?
- Laravel 13.x requires PHP 8.2+. Check the [Laravel docs](https://laravel.com/docs/13.x) for version-specific features. Use `composer require laravel/framework:^13.0` to install the latest stable release. For legacy apps, Laravel 10.x supports PHP 8.1.
- How do I install Laravel via Composer for a new project?
- Run `composer create-project laravel/laravel project-name` to scaffold a fresh Laravel app. For existing projects, add `laravel/framework` to `composer.json` and run `composer install`. Use `--optimize-autoloader` to reduce package size (~50MB).
- Does Laravel support real-time features like WebSockets or Livewire?
- Yes. Use Laravel Echo + Pusher/Redis for broadcasting, or Livewire for reactive UIs without JavaScript. For WebSockets, integrate Laravel WebSockets or use third-party packages like BeyondCode’s Laravel WebSockets. Test with `php artisan websockets:serve` in development.
- How do I migrate from Laravel 10 to 13?
- Run `composer require laravel/framework:^13.0 --with-all-dependencies` and update `config/app.php` to PHP 8.2 syntax. Check the [upgrade guide](https://laravel.com/docs/13.x/upgrade) for breaking changes (e.g., PHP 8.2 enums, typed properties). Test migrations with `php artisan migrate:fresh --seed`.
- What are the best practices for Laravel queue/job reliability in production?
- Use Supervisor or Laravel Forge to manage workers (`php artisan queue:work --daemon`). Monitor failed jobs via `failed_jobs` table and retry with `php artisan queue:retry`. For high throughput, scale workers horizontally and use Redis/SQS as the queue driver.
- Can Laravel handle serverless deployments (e.g., AWS Lambda)?
- Yes, via Laravel Vapor. Vapor compiles Laravel apps into AWS Lambda functions with minimal config. Use `php artisan vapor:deploy` after setting up your Vapor project. Note: Serverless requires stateless design; use S3 for file storage and RDS for databases.
- How do I optimize Laravel for high-traffic APIs?
- Enable API resource caching, use Laravel’s HTTP client for external calls, and batch database queries. For caching, configure Redis/Memcached in `config/cache.php`. Optimize routes with `php artisan route:cache` and use queue workers for async tasks.
- What’s the difference between Livewire and Inertia.js for Laravel frontends?
- Livewire is a full-stack framework for reactive UIs with minimal JavaScript, while Inertia.js lets you use Vue/React with Laravel’s backend. Choose Livewire for simpler apps or Inertia.js if your team prefers modern JS frameworks. Both integrate seamlessly with Blade.
- How do I secure a Laravel app against common vulnerabilities?
- Enable CSRF protection in Blade (`@csrf`), use Laravel Sanctum/Passport for auth, and validate all inputs. Keep dependencies updated with `laravel-updater` and scan for vulnerabilities via `composer audit`. For production, use HTTPS and rate limiting (`throttle` middleware).
- Are there alternatives to Laravel for PHP web apps?
- Yes. For lighter frameworks, consider Symfony (component-based) or Lumen (micro-framework). For full-stack, PHPixie or CakePHP offer alternatives. However, Laravel’s ecosystem (Nova, Forge, Vapor) and DX (Artisan, Blade) make it ideal for most projects. Evaluate based on your need for opinionated defaults vs. flexibility.
Weaver
How can I help you explore Laravel packages today?