Discussion: Composer requirement

[nhovratov]

Hi Simon,

as discussed on the train, the composer requirement and specifically the dependency to the vendors/composer/installed.json file makes it difficult to use this plugin in CI, when you only have access to separate images like node, where php is not available.

I see this is very convenient for local dev setups. Would it be possible to make this an optional dependency?

I think for most of all projects, the standard "packages/*" folder is the new best practice. So a default pattern like
packages/*/Resources/**/*.entry.{js,ts,scss,css}
could work out, as long as it can be overridden.

[s2b]

After looking into it a bit more, this approach wouldn't work because the available extensions are also used to define aliases (such as EXT:sitepackage or @sitepackage) automatically.

What probably would work is to define the extensions with their paths manually, something like this:

export default defineConfig({
    plugins: [
        typo3({
            composerPackagePaths: ['packages/sitepackage/'],
        }),
    ],
});

Edit: Adjusted to match the API from the PR

[s2b]

@nhovratov Could you check if the attached PR would fit your use case?