Laravel Workflow Kit Laravel Package

Getting Started

Install the package with Composer, then run the setup command:

composer require playerarm123/laravel-workflow-kit --dev
php artisan kit:setup

Start by reading the package README and the kit:setup command class to see exactly which files and directories it touches. The first practical use case is bootstrapping a fresh Laravel starter-kit project: after laravel new or cloning a starter kit, kit:setup prepares the .env, locale files, frontend build, and Browser test suite so the project is ready for local development and CI.

If your project already has a committed .env, locales, or build artifacts, inspect the command before running it so you understand what will be created versus preserved.

Implementation Patterns

• Project bootstrap: Run php artisan kit:setup once after creating or cloning a starter kit, before running npm install, npm run build, or the Browser test suite.
• CI integration: Add php artisan kit:setup to your CI setup step so fresh runners get the same .env, locale, build, and Browser-suite prerequisites as local development.
• Starter-kit customization: Use the command as a baseline, then layer project-specific environment variables and locale files on top. Keep custom .env values in .env.example or deployment config rather than editing generated files directly.
• Browser test workflow: Because v0.2.13 fixes the Browser suite setup on fresh projects, treat kit:setup as the first step before running Pest Browser tests. This avoids missing environment or build prerequisites.
• Composer scripts: Wire the command into a composer setup or composer test script so new contributors get a consistent first-run experience.
• Docker/devcontainer images: Run kit:setup during image build or container start for ephemeral environments, then run your normal build and test commands.

Gotchas and Tips

• Fresh-project ordering matters: v0.2.13 specifically fixes .env, locales, build, and Browser suite handling on a fresh starter-kit project. If you are on an older version, upgrade before debugging missing environment or Browser-test prerequisites.
• Existing files may not be overwritten: Setup commands often skip files that already exist. If .env or locale files are present but incomplete, inspect the command and remove or adjust the generated files deliberately.
• Node and Browser dependencies: The build and Browser suite steps likely depend on Node, npm, and a browser automation runtime. Run kit:setup after installing those prerequisites, not before.
• Environment quirks: Generated .env files may not include an application key. Run php artisan key:generate afterward if the command does not do it for you.
• Early-version churn: This is a v0.2.x package. Pin the version in composer.json and review the changelog between releases, especially around setup behavior.
• Debugging: Run the command with verbose output (php artisan kit:setup -v) to see which files are created or skipped. Check the package source if a step silently fails on your starter kit.
• Extension points: Look for publishable config or stub files via php artisan vendor:publish. Use those to customize locales, build scripts, or Browser-suite templates without forking the package.