-
Notifications
You must be signed in to change notification settings - Fork 36
problem with ExtractTextPlugin filename #85
Comments
Hi, There's something going on. It has been designed to work after Could you set up a tiny project to study? |
@bebraw here, const assetsToPurify = search.assets(
compilation.assets, options.styleExtensions
).filter(
asset => asset.name.indexOf(chunkName) >= 0
); Basically it demands |
Ok, if you could PR a fix, that would be great. |
Well I'm afraid not. This piece of code has been in there for a long time (written by you initially, see 1f67894), and I'm not entirely sure about how important it is to keep the plugin working. |
Looks like it comes from I might have some proper time for this in a few weeks. |
@bebraw How about this? Instead of filtering against Line 33 of compilation.chunks.forEach(
({ name: chunkName, files, modules }) => {
const assetsToPurify = search.assets(
compilation.assets, options.styleExtensions
).filter(
asset => files.indexOf(asset.name) >= 0
);
... Please advice for testing. |
@t47io Great start. I added a couple of comments to the PR. |
I think we solved this. Thanks for the PR. |
Uh oh!
There was an error while loading. Please reload this page.
Hi, I have seen a problem with
PurifyCSSPlugin
under production mode. Here is my code:This works perfectly fine when
DEBUG=true
, and I can see the verbose in console like:However, when
DEBUG=false
, it failed to match any assets:That's all! So I have narrowed down the problem is actually in my
ExtractTextPlugin
up there. So basically I learned this:Is this a desired behavior?
The text was updated successfully, but these errors were encountered: