Caching does not work

[buschtoens]

When processing huge or lots of .svg files, the build time gets extremely slow with the default configuration. The problem vanishes, when the optimization is disabled: optimize: false

This has two possible causes:

• If svgo is enabled, the caching doesn't work properly.
• The caching doesn't work at all.

Expected behaviour: Each .svg file is tracked individually and only re-processed, if it actually changes.

I will look into this. Originally reported in #14.

[buschtoens]

From the broccoli-caching-writer docs:

Adds a thin caching layer based on the computed hash of the input tree. If the input tree has changed, the updateCache method will be called, otherwise (input is the same) the results of the last updateCache call will be used instead.

So, seems like the whole input tree is re-processed, if even only one file changes.

[buschtoens]

I submitted an issue in broccoli-caching-writer.

I believe that caching files individually is probably out of scope and we will have to find an alternative or ship our own. I added the help-wanted label for this reason.

[buschtoens]

We can probably use broccoli-filter. I'll branch off in my fork and test something out.

broccoli-coffee is a good starting point.

[rlivsey]

Random (possibly crazy) thought, we're currently compiling n:1 which means we don't get the caching for free, could we compile 1:1 instead?

Maybe instead of compiling down to the one registry file, we compile a JS file per SVG which exports the SVG string:

// /svgs/path/to/svg.js
export default "the optimized SVG string here";

Then in the helper we can do something similar to ember-load-initializers to require the SVG as needed.