magewire-portman

To automate porting Livewire code into Magewire, configure a build pipeline that renames namespaces and merges augmentations. This process transforms upstream Livewire sources and writes the final integrated code to a dist/ directory.

The best way to keep Magewire in sync with upstream Livewire releases is to run an automated porting workflow. This workflow downloads Livewire sources, applies namespace transformations, merges customizations, and generates the ported Magewire code automatically.

You can merge custom augmentations into upstream Livewire code by defining them in a portman.config.php file. The build pipeline processes this configuration to override and customize upstream behavior during the namespace porting phase.

Yes, you need a portman.config.php file to port Livewire sources to Magewire. This configuration defines the upstream source path, augmentation directory, and output directory required to execute the end-to-end build pipeline.

Yes, you can customize Magewire behavior without modifying upstream Livewire files directly. By maintaining a separate augmentation directory, the build pipeline merges your local customizations into the upstream code during the transformation process.