I am not a bedrock user and wasn’t able to use vendor:publish using Acorn as a plugin.
After multiple trial and error, I got it working only with the previous Sage configuration by doing the composer require roots/acorn and readding the post-autoload-dump script to composer.json:
The output is correct, but if you install any package (poet, acf composer, you name it), it won’t give you the vendor:publish option for this packages. To be able to replicate, just install any of this packages with acorn as a plugin (I am using the php-8.0 release) and run wp acorn vendor:publish.
I think the reason it’s behind the fact that the plugin doesn’t have a composer.json and post-autoload-dump, but my knowledge of acorn is too limited to assess it correctly.
In a new project from scratch, using acorn as a mu-plugin, and requiring log1x/poet it gives this:
Which provider or tag's files would you like to publish?:
[0] Publish files from all providers and tags listed below
[1] Provider: Roots\Acorn\Providers\AcornServiceProvider
[2] Tag: acorn
I tried wp acorn vendor:publish --tag=acorn or selecting number 0 or number 1, and it sets up the config folder but it still doesn’t work.
In the documentation, it says to execute wp acorn vendor:publish --tag=acorn:init, which also doesn’t expand the list.
In the other project, where I required acorn from the sage folder and added post-autoload-dump, it gives me:
Which provider or tag's files would you like to publish?:
[0] Publish files from all providers and tags listed below
[1] Provider: Log1x\AcfComposer\Providers\AcfComposerServiceProvider
[2] Provider: Log1x\Poet\PoetServiceProvider
[3] Provider: Log1x\SageSvg\SageSvgServiceProvider
[4] Provider: Roots\Acorn\Providers\AcornServiceProvider
[5] Tag: acorn
[6] Tag: config
>