The usefulness of the "changed" plugin

[ghost]

trafficstars

Hi Juan!

Could you explain more clearly the usefulness of the "changed" plugin?

What would be the purpose? Why would anyone want to monitor the files that have been compiled?

//only pass unchanged *main* files and *all* the partials
.pipe(changed('dist', {extension: '.html'}))

Thank you for publishing this package :)

[juanfran]

Hi @joelcipriano

it is for performance, if your project has dozens of .jade the compilation could take too long

[ghost]

Sorry @juanfran, but I still do not understand. If only .jade files are monitored for changes, why listening .html files that already have been compiled?

[juanfran]

bacause gulp-changed checks the last modified date, if example.html is less recent than example.jade then gulp-changed pass through example.jade

sorry if I haven't explained well

[ghost]

Ok. Got it!

Have you tested with more than 100 files? I used this solution in a project with 62 pages and 108 includes. The CPU usage hit the sky and the compilation stopped working :/

[juanfran]

at the beginning or after a change? I have a project with many files too and it works well https://github.com/taigaio/taiga-front/blob/master/gulpfile.js

[siliconalchemy]

This has gone a little off-topic, but I get the same 'hanging'. Using gulp-changed works fine for me, that's not an issue. But if I use jade-inheritance on watched include files, which triggers recompile of 65 jade files it takes several minutes and hangs gulp at 100% cpu. Most of that time is spent in futex by an strace.