Weave Code
Nova Devtool Laravel Package
laravel/nova-devtool
Nova Devtool streamlines Laravel Nova component development with a Workbench-based Nova setup, one-command installs for common frontend deps, and easy toggles to enable/disable Vue DevTools in Nova’s compiled assets.
Devtool for Laravel Nova Development
Frequently asked questions about Nova Devtool
- How do I quickly set up a Laravel Nova development environment with this package?
- Run `composer require --dev laravel/nova-devtool` and `npm install --save-dev @laravel/nova-devtool`, then initialize the Workbench with `php vendor/bin/testbench nova:devtool setup`. This creates a `workbench` directory with a pre-configured Nova instance. Serve it locally via `composer run serve`.
- Does laravel/nova-devtool work with Laravel Nova v4 or only newer versions?
- The package supports Laravel Nova v4+ but includes a `nova.mix.js` replacement via `mix.extend('nova', ...)` for easier migration. Check the package’s `composer.json` for exact Nova version compatibility, as it aligns with Laravel’s supported Nova releases.
- Can I use this package in production, or is it only for development?
- This package is **dev-only** and should **never** be included in production. It adds Workbench, Vue DevTools, and frontend dependencies (Axios, Lodash, Tailwind) that are unnecessary for live environments. Exclude it from your `composer install --no-dev` workflows.
- Will this package conflict with existing Laravel testing tools like Pest or PHPUnit?
- Yes, it relies on **Orchestra Workbench**, which may conflict with Laravel’s built-in testing tools. Workbench uses shared state (e.g., sessions, storage), so if you’re using Pest/PHPUnit, you’ll need to configure them to avoid clashes or use Docker/Laravel Sail for isolation.
- How do I enable/disable Vue DevTools for Nova’s compiled assets?
- Use the commands `php vendor/bin/testbench nova:devtool enable-vue-devtool` or `disable-vue-devtool`. These toggle Vue DevTools in Nova’s builds without manually editing Webpack config. Disable it before deploying to production to avoid exposing debug tools.
- Does this package automatically install Axios, Lodash, Tailwind CSS, and Vue?
- Yes, running `php vendor/bin/testbench nova:devtool install` adds these dependencies to your `package.json`. However, manually curate them if you’re working on a large project to avoid version conflicts or unused CSS/JS bloat in your main application.
- Can I use laravel/nova-devtool with Docker or Laravel Sail?
- Workbench can run in Docker, but configuration may differ from native setups. If using Sail, ensure your `docker-compose.yml` includes Workbench’s dependencies. Alternatively, consider running Workbench in a separate container to avoid conflicts with your main Laravel app.
- What if I only need to develop a single Nova tool or field—is this package still useful?
- Yes, the package’s **Workbench setup** provides an isolated Nova environment for testing tools, fields, or cards without polluting your main project. The one-command dependency installation (Axios, Vue, etc.) also saves time if you’re prototyping frontend-heavy components.
- How does this compare to Nova’s built-in `php artisan nova:install` or custom Docker setups?
- Unlike `nova:install`, this package **pre-configures Workbench + frontend tools** in one step, reducing setup time. Custom Docker setups offer more isolation but require manual configuration. Choose this package for **rapid local development**; opt for Docker if you need CI/CD compatibility or stricter environment separation.
- Will this package work with Laravel 10.x but not older versions?
- The package requires **Laravel 10.x+** (Nova’s minimum version) and **PHP 8.1+** for Workbench compatibility. If you’re on Laravel 9 or older, you’ll need to check Nova’s version support or use alternative tools like `nova:install` with manual Workbench setup.
Weaver
How can I help you explore Laravel packages today?