When making a kit composer updatable (by setting updatable: true introduced by https://github.com/statamic/cms/pull/11064), you're likely going to want to provide your own package service provider class, PSR-4 namespace, vendor views, etc. that are separate from export_paths (which get installed into the users app, rather than remaining in vendor). Right now there is no way to automatically export those vendor files to your starter kit repo.
The Solution
In this PR, we now expect a package folder in your dev application for all your package's vendor files...
These files will be exported to the root of your shippable repo when running starter-kit:export.
We also export all of your files export_paths to an export folder in your shippable repo to keep things clean and free from filename conflicts.
This lets you manage your package's composer.json, etc. from the package folder, and the exporter and installer will intelligently put Everything in Its Right Place, just like Radiohead.
Think of the exported directory similar to a compiled assets directory when using a build tool like Vite. You export/generate files into this directory, and shouldn't touch it manually.
The Problem
When making a kit composer updatable (by setting
updatable: trueintroduced by https://github.com/statamic/cms/pull/11064), you're likely going to want to provide your own package service provider class, PSR-4 namespace, vendor views, etc. that are separate fromexport_paths(which get installed into the users app, rather than remaining invendor). Right now there is no way to automatically export those vendor files to your starter kit repo.The Solution
In this PR, we now expect a
packagefolder in your dev application for all your package's vendor files...These files will be exported to the root of your shippable repo when running
starter-kit:export.We also export all of your files
export_pathsto anexportfolder in your shippable repo to keep things clean and free from filename conflicts.For example, if this is your dev app...
Then this is what the final export will look like...
This lets you manage your package's
composer.json, etc. from thepackagefolder, and the exporter and installer will intelligently put Everything in Its Right Place, just like Radiohead.Think of the exported directory similar to a compiled assets directory when using a build tool like Vite. You export/generate files into this directory, and shouldn't touch it manually.
Todo