Skip to content

Conversation

@Hugoer
Copy link
Member

@Hugoer Hugoer commented May 7, 2025

This PR adds support for generating .content.xml and css.txt files for CSS files created dynamically during the build process (e.g., via PostCSS plugins).
These files are essential for enabling AEM to recognize and serve the generated clientlibs correctly.

Description

  • Introduced a new extraEntries configuration option in PostCSS processing to allow metadata generation for target files.
  • Supports specifying:
extraEntries: {
  extension: 'css',
  cwd: destinationPath,
  filenamePattern: 'clientlibs-*',
}
  • Ensures metadata is generated for CSS files matching the given pattern in the specified output directory.

Related Issue

Fixes #126

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • I have read the CONTRIBUTING document.
  • All new and existing tests passed.

@Hugoer Hugoer requested review from easingthemes and filipdx3 May 7, 2025 15:29
@Hugoer Hugoer added the enhancement New feature or request label May 7, 2025
@Hugoer Hugoer merged commit 4004ca1 into Netcentric:main May 9, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support clientlib metadata generation for dynamically created CSS files

2 participants