laravel-package-specialist_skill

Overview

This skill provides hands-on guidance for developing, integrating, and maintaining Laravel Nova packages and forked repositories. It focuses on Nova field/tool development, webpack.mix configuration for Nova 5.x (Vue 3), composer path repositories, and reliable workflows for building and syncing forks. Practical commands, package structure patterns, and troubleshooting steps are included to speed up iteration and deployment.

How this skill works

I inspect package layout under packages/*, the package composer.json, the webpack.mix.js externals and output settings, and the Nova service provider registration. I validate build steps (npm run dev/prod), composer path repository entries, and the recommended build/commit order so changes propagate to the main app via symlinked vendor entries. I also guide on syncing forks with upstream and resolving common webpack, Vue, or composer errors.

When to use it

• Creating or updating a Laravel Nova field, tool, resource, or lens
• Integrating forked packages from pcrcard/* into the main app using path repositories
• Configuring webpack.mix.js for Nova 5.x and Vue 3 components
• Building, committing, and deploying package assets (dist/) for Nova
• Troubleshooting missing components, webpack externals, symlink issues, or composer path problems

Best practices

• Always build assets inside the package directory and commit dist/ files to the package repo
• Keep externals configured (vue, laravel-nova, laravel-nova-ui) to avoid bundling Nova/Vue
• Commit package changes to the package repo first, then update the main app with composer
• Use @dev path repository entries for local development and semantic version tags for releases
• Avoid committing node_modules; rebuild symlinks with composer install when needed

Example use cases

• Add a new Nova FormField Vue component and register it via resources/js/field.js, then publish via the package service provider
• Fork an upstream nova package, adjust composer namespace to pcrcard/*, add it to packages/, and wire it into the main app via composer path repo
• Fix a blank Nova field by verifying $component matches app.component registration and rebuilding assets
• Resolve webpack errors by ensuring externals map vue and laravel-nova to their global names and setting uniqueName in output
• Sync a fork with upstream: add upstream remote, fetch, merge/rebase, rebuild assets, and update the main app