TYPO3 Vendor Bundler config
Configuration for TYPO3 Vendor Bundler, a Composer library to bundle vendor libraries for TYPO3 extensions in classic mode
| Type | object |
|---|---|
| File match |
typo3-vendor-bundler.json
typo3-vendor-bundler.yaml
typo3-vendor-bundler.yml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/typo3-vendor-bundler-config/latest.json |
| Source | https://raw.githubusercontent.com/eliashaeussler/typo3-vendor-bundler/refs/heads/main/res/typo3-vendor-bundler.schema.json |
Validate with Lintel
npx @lintel/lintel check
Properties
3 nested properties
When enabled, the autoload bundler will be included when executing composer bundle.
When enabled, original contents of the root composer.json file will be backed up in a separate file
Absolute or relative paths to files to remove from parsed vendor libraries class map
3 nested properties
When enabled, the dependency bundler will be included when executing composer bundle.
4 nested properties
Can be a JSON or XML file. Relative paths are resolved based on the vendor libraries path.
All BOM versions supported by CycloneDX can be used.
When enabled, all dev dependencies will be included in the generated SBOM. Otherwise, only production dependencies will be included.
When enabled, the configured SBOM file will be overwritten with serialized SBOM, if the file already exists.
When enabled, original contents of the root composer.json file will be backed up in a separate file
2 nested properties
When enabled, vendor libraries will be extracted from root composer.json, if no separate composer.json for vendor libraries exists already.
When enabled, extraction will fail if problems are encountered during extraction, e.g. if packages cannot be resolved.
This path will be used to calculate paths to configured files if they are configured as relative paths. If the root path is configured as relative path, it is calculated based on the config file path.
Definitions
When enabled, the autoload bundler will be included when executing composer bundle.
When enabled, original contents of the root composer.json file will be backed up in a separate file
Absolute or relative paths to files to remove from parsed vendor libraries class map
When enabled, the dependency bundler will be included when executing composer bundle.
4 nested properties
Can be a JSON or XML file. Relative paths are resolved based on the vendor libraries path.
All BOM versions supported by CycloneDX can be used.
When enabled, all dev dependencies will be included in the generated SBOM. Otherwise, only production dependencies will be included.
When enabled, the configured SBOM file will be overwritten with serialized SBOM, if the file already exists.
When enabled, original contents of the root composer.json file will be backed up in a separate file
Can be a JSON or XML file. Relative paths are resolved based on the vendor libraries path.
All BOM versions supported by CycloneDX can be used.
When enabled, all dev dependencies will be included in the generated SBOM. Otherwise, only production dependencies will be included.
When enabled, the configured SBOM file will be overwritten with serialized SBOM, if the file already exists.
When enabled, vendor libraries will be extracted from root composer.json, if no separate composer.json for vendor libraries exists already.
When enabled, extraction will fail if problems are encountered during extraction, e.g. if packages cannot be resolved.