What's happening
I tried to migrate project to CRA5 and Craco 7 and encountered strange behavior, listed in title. Setting style.postcss.plugins, both via array and function, doesn't affect resulting webpack config. Apparetnly it also happens with env field.
What should happen
Resulting webpack config should be modified and include any custom configuration that is provided in craco.config.js.
To reproduce
Set up a project with CRA, add CRACO. Then include some postcss plugins and list them in style.postcss.config as listed in CRACO's docs.
Now when you start project you should notice that postcss plugins didn't work.
You can also go to node_modules/@craco/craco/dist/lib/features/webpack/override.js and log resultingWebpackConfig to the console to check that postcss config wasn't affected.
What's happening I tried to migrate project to CRA5 and Craco 7 and encountered strange behavior, listed in title. Setting
style.postcss.plugins
, both via array and function, doesn't affect resulting webpack config. Apparetnly it also happens withenv
field.What should happen Resulting webpack config should be modified and include any custom configuration that is provided in
craco.config.js
.To reproduce Set up a project with CRA, add CRACO. Then include some postcss plugins and list them in
style.postcss.config
as listed in CRACO's docs. Now when you start project you should notice that postcss plugins didn't work.You can also go to
node_modules/@craco/craco/dist/lib/features/webpack/override.js
and logresultingWebpackConfig
to the console to check that postcss config wasn't affected.CRACO version 7.1.0
CRACO config
package.json