search

Crunch / postcss-less

MIT License
35 stars 9 forks source link

Slower than re-parsing #5

Open stevenvachon opened 8 years ago

stevenvachon commented 8 years ago

My compile times have increased from 3.5s to 4.3s, when compared to running less.js separately from postcss.

matthew-dean commented 8 years ago

Okay? The only purpose of this plugin is to add Less to a PostCSS workflow. If you don't need to do that, then don't do that?

stevenvachon commented 8 years ago

We already could add Less to a PostCSS workflow by re-parsing strings. There should be some sort of advantage to using this, no?

matthew-dean commented 8 years ago

Well, theoretically... but to be honest, I never benchmarked the difference. There was no specific PostCSS plugin, but I think what you mean is that you could use Gulp to pass the Less result to PostCSS.

That's interesting. I would have thought that parsing twice is inevitably slower. In fact, I wonder if there's not some other variable at play. Source map generation? Happening in one workflow and not another? How are you benchmarking, and could you add that benchmarking to this repo?

stevenvachon commented 8 years ago

No benchmarking, just compared consistent compile times. The 1 second difference does affect workflow when using gulp watches.