Weave Code
Nova Tinker Tool Laravel Package
beyondcode/nova-tinker-tool
Nova Tinker Tool adds an interactive Artisan Tinker console to Laravel Nova, letting admins run PHP and tinker commands directly from the dashboard without opening a terminal. It speeds up debugging, quick data checks, and experimentation in a familiar Nova interface.
Use Laravel tinker from Nova.
Frequently asked questions about Nova Tinker Tool
- How do I install beyondcode/nova-tinker-tool in Laravel Nova?
- Install it with composer require beyondcode/nova-tinker-tool, then register the tool in your NovaServiceProvider tools() method. There are no migrations, schema changes, or meaningful configuration files involved. Because the package is archived and dates from 2020, pin it and verify it against your Nova major before relying on it.
- Which Laravel Nova versions does nova-tinker-tool support?
- That is not clearly established. The package was last released on 2020-01-30, and Nova's tool API changed materially across Nova 1, 4, and 5, so a 2020-era tool is unlikely to mount cleanly on a current install without patching. Test it on your exact Nova major or plan to fork and update the component API yourself.
- Is nova-tinker-tool safe to use in production?
- Treat it as remote code execution behind a Nova dashboard: any Nova user who can reach the panel can read, mutate, or destroy data and execute PHP as the application. Nova's default authorization does not automatically contain this, so restrict it to a named user or role allowlist and preferably a non-production environment. Add audit logging, timeouts, and output caps before considering production use.
- How do I restrict access to the Nova Tinker Tool?
- Enforce authorization beyond Nova's default gate by using a tool-level canSee or authorize check tied to a specific user or role allowlist. Scope it to internal engineering or senior support users and avoid broad Nova access, customer-facing installs, partner-accessible dashboards, and multi-tenant Nova setups. Environment scoping, such as disabling it outside staging, is also strongly recommended.
- Does nova-tinker-tool log or audit tinker commands?
- There is no built-in audit record described for the tool. If you adopt or fork it, add logging around every execution that captures the user, timestamp, code, and result in a retained log. That audit trail is essential because the panel executes arbitrary PHP with application credentials.
- What Tinker version does nova-tinker-tool require?
- The 1.1.0 changelog claims Tinker 2.0 support, but that is internally inconsistent with a package archived in 2020, since Tinker major versions now track Laravel's release cadence. Verify the actual Tinker invocation path against your installed Tinker major and PHP version; Tinker 2.x implies PHP 8.2 or newer. Do not trust the changelog until it is proven in a fork.
- Is nova-tinker-tool still maintained?
- No. The repository record shows it archived, with the last release on 2020-01-30 and zero dependents. The realistic choice is adopt versus reimplement the pattern, because long-term ownership lands on your team either way. If you use it, fork it into an internal repository and pin it against your Nova major.
- What are alternatives to nova-tinker-tool?
- A minimal internal replacement can wrap Artisan::call('tinker', ['--execute' => $code]) behind a guarded route or a small custom Nova tool. That gives you control over authorization, environment scoping, audit logging, timeouts, and output caps. Compare the fork-and-own cost of the archived package against that small internal build.
- Can I run tinker commands from Laravel Nova without a terminal?
- Yes. Nova Tinker Tool adds an interactive Artisan Tinker console to the Nova dashboard so admins can run PHP and tinker commands without opening a terminal. It is intended for quick debugging, data checks, and experimentation inside a familiar Nova interface. Because it executes arbitrary PHP, use it only on an internal operations surface.
- How do I test nova-tinker-tool compatibility before adopting it?
- Build a small compatibility matrix for your Nova major and Tinker major, then install the package in staging and confirm tool registration, Vue component mounting, and the Tinker invocation path. Exercise it on Nova 4 or 5 if those are your targets, and check whether any timeout, output cap, or destructive-statement guardrail exists around the REPL. Given the archive status, test a forked and patched version rather than assuming Packagist forward compatibility.
Weaver
How can I help you explore Laravel packages today?