Weave Code
Laravel Tinker Server Laravel Package
beyondcode/laravel-tinker-server
Run Laravel Tinker commands on remote servers through a simple HTTP endpoint. Tinker Server exposes an authorized route so you can execute PHP and inspect your app from anywhere, ideal for serverless and Vapor deployments where SSH access isn't available.
Tinker with your variables while working on your application.
Frequently asked questions about Laravel Tinker Server
- Does beyondcode/laravel-tinker-server work with Laravel 10, 11, or 12?
- No. Treat it as incompatible until a spike proves otherwise: the last release was 2019-02-14, the repository is archived, and the dependency graph is pinned to PHP 7.x and Laravel 5.x. On PHP 8.1+ with Laravel 9, 10, 11, or 12 the constraints against illuminate/* and psysh will very likely fail to resolve, and forcing resolution runs into PHP 8 serialization and Reflection changes that sit directly in this package's execution path.
- How do I install beyondcode/laravel-tinker-server?
- Install it as a dev-only dependency with composer require --dev beyondcode/laravel-tinker-server, publish the config file, and run php artisan tinker-server to boot the local listener. The package is auto-discovered on Laravel 5.5+ and exposes a single global helper, ts($var), plus one publishable config file. All of this only applies on a legacy PHP 7.x stack, so verify Composer resolution before opening a ticket.
- Is it safe to run laravel-tinker-server in production?
- No. A listener that receives values and evaluates PHP inside a fully bootstrapped application is effectively a remote shell, not a telemetry channel. Dev .env files routinely carry staging and production credentials, so exposing the port on a shared host, a forwarded devcontainer port, or a Codespace is RCE-adjacent. This needs a written policy statement a PM endorses, not individual discretion.
- How does the ts() helper work with Laravel Tinker Server?
- ts($var) is a global helper that forwards a value out of the running application to the tinker-server listener, where PsySH, the same REPL behind php artisan tinker, exposes it as a live $variable. You can then drill into a model, collection, or config array interactively instead of halting the request with dd() or spraying dump() into a response. Remember that REPL-side mutations do not write back to the live application.
- What is the best alternative to laravel-tinker-server for remote debugging?
- For day-to-day local work, use php artisan tinker, dd(), dump(), Ray, or Xdebug; for structured runtime inspection, Laravel Telescope. For remote and serverless targets, prefer first-party or maintained tooling such as Vapor CLI commands over an archived package. beyondcode/laravel-tinker-server has 203 stars and zero dependents, which is a signal that interest in the approach has never translated into production adoption.
- Why won't laravel-tinker-server install on PHP 8.1 or newer?
- The package's Composer constraints are pinned to PHP 7.x and Laravel 5.x, so resolution against modern illuminate/* and psysh versions fails before installation even starts. Even a forced resolution runs into PHP 8 serialization and Reflection changes, which sit directly in this package's path. Both the socket transport and the PsySH integration live close to PHP internals, the code least likely to survive an upgrade.
- Can I use laravel-tinker-server with Laravel Vapor or serverless deployments?
- The serverless case is exactly what the package was pitched for, since Vapor deployments have no SSH access. In practice, an archived package pinned to PHP 7.x cannot run on modern Vapor runtimes, so you would need to fork and repin it before it is even testable. Treat that as a build decision, not a dependency decision.
- Does laravel-tinker-server serialize Eloquent models, closures, and resources correctly?
- Partly, and that is the trap. Values cross a process boundary, so closures, resources, PDO connections, and some Eloquent graphs degrade or fail outright; object identity is lost and REPL-side mutations never write back. A developer who reads this as a live debugger will misdiagnose their own application, and that false confidence never shows up in a trial log.
- Is beyondcode/laravel-tinker-server still maintained?
- No. The repository is archived, the last release was 2019-02-14, and there is no advisory or CVE-response process, which means no upstream fix will ever arrive. Every future incompatibility becomes yours to absorb. Removal is mechanical, but only if you never let it creep beyond dev dependencies and ts() calls.
- How do I remove laravel-tinker-server from a codebase, and what does forking it involve?
- Removal is mechanical: drop the --dev Composer dependency and delete the ts() calls, and there are no routes, migrations, or production code paths to audit because it sits beside the request lifecycle rather than inside it. Forking is the harder path, since you would need to repin illuminate/* and psysh plus address PHP 8 serialization and Reflection behavior. Scope that as an engineering build with ongoing maintenance, not a quick Composer bump.
Weaver
How can I help you explore Laravel packages today?