honestly, I have no idea what that block does (if anything), so that could solve everything, or it might solve nothing 😆
does it has something to with exposing the files? (although expose is a different block)
¯_(ツ)_/¯ that’s a question for someone much better versed in how composer works than I am lol
it's the bit that says "from the recipes, these files have been copied and should not be copied again."
Because they become a part of your project, and should not be overwritten (as opposed to e.g.
resources from vendor, js/css should be updated when ever)
@Nightcrawler can you confirm that Page.php file exist in the host server that you works on? if you run
composer create-project in local, there are bunch of files like Page.php / PageController.php, etc will be created for you and awaiting you add the meat to the bone, but if you you run
composer install or 'composer update` in the server, the block mentioned by @Joe will be not effect hence will not create those files for you.
@Nightcrawler though I am not sure what
composer require will behave in that
project-files-installed light spot.
I didn't do a composer-create, I copied the files from my 'base project' but yes, they definitely exist on the host server along with the composer.json that will be executed.
autoloader might be missing them.