fix(css-modules): replace literal [local] placeholder in production .… #7588
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix CSS class name generation for
.module.lessfiles in production builds: the literal[local]placeholder was not expanded, producing names likeComponent-module__[local]___Abc12. It is now correctly replaced, yieldingComponent-module__container___Abc12.Context / Problem
In production (
dev=false), thewebpack-less-pluginprovides a customgetLocalIdent. WhengetLocalIdentis defined,css-loaderskips its usual post-processing oflocalIdentName. Our implementation calledinterpolateNamedirectly, which doesn’t know the[local]token, leaving it untouched.Observed:
Expected:
It went unnoticed because in development mode (
dev=true) the customgetLocalIdentisn't applied.Reproduction Steps
Example.module.less:[local].pnpm --filter @plone/volto start) the name is correct.Implemented Solution
In webpack-less-plugin.js, inside
getLocalIdent:[local]occurrences withlocalNamebefore callinginterpolateName.Risks / Impact
.module.lesschange (now correct). Any global overrides relying on the buggy literal[local]will stop working (expected).Closes #7587