Issue with plugin sequencing(CopyWebpackPlugin runs before postcss-assets-webpack-plugin) #18159
Unanswered
murtuzasyed
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I upgraded webpack from V4 to v5 and seeing an issue with
postcss-assets-webpack-plugin
getting css files that aren't part of the webpack process rather static resource that are being copied using theCopyWebpackPlugin
. In others words, whilepostcss-assets-webpack-plugin
is waiting for assets theCopyWebpackPlugin
is doing the copy operation and the copied files become part of the assets provided topostcss-assets-webpack-plugin
. In V4 this didn't happen and Copy would execute at the end.I have a sample project here that uses v5 and other compatible dependencies. Here's the plugin section.
Anyone seen this before?
Beta Was this translation helpful? Give feedback.
All reactions