Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slower than re-parsing #5

Open
stevenvachon opened this issue Jul 12, 2016 · 4 comments
Open

Slower than re-parsing #5

stevenvachon opened this issue Jul 12, 2016 · 4 comments

Comments

@stevenvachon
Copy link

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

@matthew-dean
Copy link
Member

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
Copy link
Author

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
Copy link
Member

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants