You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have faced an issue while working with an extraordinary large CSS file (almost 150k lines)
It looks like grunt-critical is not able to process the full file. Instead of that the generated critical contents are a very small portion of the original file. So, there is no visible error but it is clearly not good.
If we split that input file into 3-4 parts then it creates bigger contents, but we don't really trust in this approach because it looks like that internally we are yet losing some rules.
We wonder if there is any chance to increase any internal buffer or provide a magic parameter in order to fix this issue.
Is there anything we can do (apart from reducing the size of the input file)?
Thanks and regards
The text was updated successfully, but these errors were encountered:
We have faced an issue while working with an extraordinary large CSS file (almost 150k lines)
It looks like grunt-critical is not able to process the full file. Instead of that the generated critical contents are a very small portion of the original file. So, there is no visible error but it is clearly not good.
If we split that input file into 3-4 parts then it creates bigger contents, but we don't really trust in this approach because it looks like that internally we are yet losing some rules.
We wonder if there is any chance to increase any internal buffer or provide a magic parameter in order to fix this issue.
Is there anything we can do (apart from reducing the size of the input file)?
Thanks and regards
The text was updated successfully, but these errors were encountered: