question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Performance issues

See original GitHub issue

Hi, thank you for this great plugin. I’m running to some performance issues with a big project. Due the multiple bundles generated (one with and one without css), the build time increases significant (at least double in production with minification) in comparision with just extract-css-webpack-plugin . It also seems to me, that the no_css get’s generated when there is no css imported at all.

In my case it goes from 6 minutes to 16 Minutes.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:21 (21 by maintainers)

github_iconTop GitHub Comments

1reaction
BowlingXcommented, Jun 18, 2017

I was trying to find a better solution for removing the stuff from the initial chunk, without reiterating and removing the styles with the regex. I found something that actually keeps the style-loader in the async chunks and I just apply the extraction to the initial chunk. It was a bit hard to get my head around it due the complex structure and not much documentation, but I think it’s working properly.

All tests also still work and it does not require manual adding any hot reload stuff (it will keep everything from the style-loader).

I did not made any more modifications that you added (for example extracting the async css files and more). Maybe this is a good base to extend your version.

here is the pull-request: https://github.com/webpack-contrib/extract-text-webpack-plugin/pull/546

1reaction
faceyspaceycommented, Jun 17, 2017

here’s a short private/unpublished launch article im releasing in a few days:

https://medium.com/@faceyspacey/extract-css-chunks-webpack-plugin-chunkify-your-css-a-few-things-you-need-45cb474cc332

feedback is much appreciated. trying to make this as obvious to people as possible. anything i should strip away or add? or say better?

…guys help me get this (as in the package in general) ready for prime time. we all know its very needed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Dealing with Performance Problems
Types of Performance Problems ; Quantity of work (untimely completion, limited production). Poor prioritizing, timing, scheduling; Lost time ; Quality of work ( ......
Read more >
Handling Performance Issues With Grace
Low Productivity or Late Completion – Make sure you've been clear about the requirements and expectations of the job. · Poor Quality of...
Read more >
Top 5 Common Performance Problems
Top 5 Common Performance Problems · Shallow Work · Inability to Prioritize · False Sense of Urgency · Productive Procrastination · Low-Quality Output....
Read more >
68 Examples of Performance Problems
Overreaction to Criticism, Passive Aggressive Behavior ; Poor Attention to Detail, Poor Budget Control ; Poor Listening Habits, Poor Work Quality.
Read more >
5 Common Reasons for Performance Issues (Plus 3 Tips to ...
Most Common Causes of Performance Issues · 1. They lack knowledge or skill. · 2. They have unclear or unrealistic expectations. · 3....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found