Add build configuration to Site package instead of project root

[Kleisli]

What should be improved?

On one hand personally I like to have the frontend build stack including node_modules inside the Private Resources folder of my Site packages, but I also think about distribution of Site packages.

Currently the configuration defaults are copied to the root of a project, and the Styles and Scripts are built within the Site packages, but for portability or when I want to publish a Site package, I can only ship it with the built assets and they can't be changed and built again without manually copying the configuration files to the root.

Describe the solution you would like

I'm not sure what works best, but a solution could be a carbon pipeline command controller that takes care of the initialization instead of the "installer-resource-folders" in composer that always copies to the root.
./flow carbon.pipeline:init would copy the files to the root like the current way
./flow carbon.pipeline:init Vendor.Site would copy the files to DistributionPackages/Vendor.Site
in the second case the paths to the build scripts would have to be adjusted to ../../Build/Carbon.Pipeline

but I don't get if the build scripts have to be adjusted too.

Possible alternatives

No response

Additional context

to be honest I didn't try it yet, but if you are okay with the idea, I would first test it manually to add all the files to a site package and could also write the command controller. I couldn't help with the javascript though..

Are you willing to work on this?

• Yes, I would like to help

[jonnitto]

Sorry, that I didn't answer you yet. Yes, please start a PR, I'm sure we can handle all js troubles ;-)

[jonnitto]

Commands are not available for neos-build packages.
But I've figured out on how to run some actions on composer update:

Based on that, we could add an additional question

[jonnitto]

@Kleisli Are you still interested in this?

[Kleisli]

Hej @jonnitto Sorry, I was quite busy this year with different things...
But thank you, this looks very nice. :-)

I just tried to set that up manually in a new project, but there is one thing that are currently not resolvable.. I have two requirements that are not compatible

1. having the build configuration files and installing the node_modules in DistributionPackages/My.Site/Resources/Private/Frontend
2. installing the the generic build scripts as dependencies e.g. in Build/Carbon.Pipeline

this only works when I copy all the build scripts into the site package, because the scripts can't auto-find their dependencies when they are installed in a subfolder. And I only want the configuration files for building in my site package, but install the build scripts as a dependency.

I have limited understanding of node.js, but I think this could work if the build scripts were installed with the node module instead of the Neos package.