Allow modules
options without disabling autoModules
#291
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.
This adds an explicit
autoModules:true
option that forces isModuleFile() behavior even ifoptions.modules
is truthy. This is important becauseoptions.modules
can be necessary to configure the behavior of postcss-modules, but currently doing so also forces postcss-modules to be run on 100% of files.Example:
Current Behavior:
The above object value for
options.modules
is truthy, which causespostcss-modules
to be executed against all files.Behavior with this change:
Since
autoModules
is explicitly set totrue
,options.modules
being a (truthy) object does not override automatic module behavior, sopostcss-modules
is only executed against files ending in.module.css
.