Laravel Package Specialist

Forked package management uses Composer path repositories to wire local package forks into your main app. Configure Laravel Mix webpack and implement PHP field classes, Vue components, and assets for Nova packages like nova-menus or nova-medialibrary-bounding-box-field, then install via Composer path repositories instead of Packagist.

Yes. Composer path repositories let you install packages from local directories or VCS forks, enabling local development workflows. Point your composer.json to the forked package path, install dependencies, build with webpack, and test integration without publishing to Packagist.

Clone or update your forked package repository, install dependencies, configure Laravel Mix webpack.config.js for asset compilation, implement PHP field classes and Vue components, then register the package in your main app using Composer path repositories for seamless integration and deployment.

Create PHP field classes in your forked package that extend Nova's base classes, build corresponding Vue components for the frontend, configure Laravel Mix to compile assets, and use webpack to bundle them. Install via Composer path repositories to make fields available in Nova resources and tools.

You need a Laravel Nova installation, Composer for dependency management, Node.js and npm or yarn for webpack asset compilation, and a forked package repository. Set up Laravel Mix webpack.config.js to handle asset building alongside PHP field and Vue component development.

Yes. Git submodules and Composer path repositories work together in VCS workflows. Submodules track forked package repositories while Composer path repositories wire them into your app, enabling coordinated versioning and deployment across multiple interconnected packages.