Weave Code
Tinker Laravel Package
laravel/tinker
Laravel Tinker is a powerful REPL for Laravel, letting you interact with your application from the command line. Run Artisan’s tinker command to test code, inspect models, and debug quickly in an interactive shell.
Powerful REPL for the Laravel framework.
Frequently asked questions about Tinker
- How do I install Laravel Tinker in my Laravel project?
- Run `composer require laravel/tinker --dev` to install it as a development dependency. No additional configuration is needed—just execute `php artisan tinker` to start the REPL.
- Can I use Laravel Tinker to test Eloquent queries without writing temporary routes?
- Yes! Tinker lets you interact with Eloquent models directly. For example, type `User::where('active', true)->get()` to test queries in real time, or inspect relationships with `User::with('posts')->first()`.
- Does Laravel Tinker work with Laravel 13 and PHP 8.5?
- Yes, Laravel Tinker v3.x supports Laravel 10–13 and PHP 8.1–8.5. Check the [Laravel documentation](https://laravel.com/docs/artisan#tinker) for version-specific details and deprecation notes.
- How can I customize the output of Tinker for my domain objects (e.g., DTOs or API responses)?
- Use **casters** to format custom objects. Register them via `Tinker::cascade()` or `Tinker::alias()` in your `AppServiceProvider`. For example, alias a complex object to a readable string for debugging.
- Is Laravel Tinker safe to use in CI/CD pipelines for data seeding or validation?
- Yes, but use the `--execute` flag carefully. For example, `php artisan tinker --execute='User::factory()->count(10)->create()'` runs commands non-interactively. Restrict this to trusted pipelines to avoid command injection risks.
- Will Laravel Tinker slow down my production environment?
- No, Tinker is a development-only tool with no runtime overhead. It’s installed as a `--dev` dependency and doesn’t affect production builds or performance.
- How do I debug failed Laravel jobs or queues using Tinker?
- Access the job payload directly in Tinker. For example, if a job failed, inspect its data with `$job->payload()` or re-run it interactively using `dispatch(new YourJob($data))` after fixing issues.
- Are there alternatives to Laravel Tinker for debugging Laravel apps?
- Other REPL tools like **PsySH** (standalone) or **PHPStorm’s built-in REPL** work, but Tinker is Laravel-optimized with built-in support for Eloquent, service containers, and Artisan. It’s the most seamless choice for Laravel developers.
- Can I use Laravel Tinker to inspect Laravel’s service container or bindings?
- Absolutely. Tinker gives you direct access to the container. For example, type `app('cache')` to inspect cache bindings or `app()->bindings()` to list all registered services.
- How do I integrate Tinker with VS Code or PHPStorm for better autocompletion?
- Install the **Laravel Artisan** extension in VS Code or use PHPStorm’s built-in REPL support. Tinker works with IDE plugins that recognize Artisan commands, but custom casters may require PsySH plugin setup for full autocompletion.
Weaver
How can I help you explore Laravel packages today?