plugin-cache for fourseven:scss gets insanely huge

[derwaldgeist]

• Feature request
• Bug report
• Question

meteor version: 1.10.2

fourseven:scss version: 4.12.0

I was wondering why my .meteor folder was so huge (over 6 GB). I found out that 3 GB alone are allocated by plugin-cache/fourseven_scss. What is the reason for this cache size? And is there any way to get this down regularly?

Another 1.8 GB are used by bundler-cache. Not sure where this comes from.

[brettg2]

+++++++++++++++++++++++++++++++++1

Cache folder was last reported at 26 gigs!!

[copleykj]

From looking at how caching works, it seems that the caching-compiler package uses the lru-cache package. From the documentation of that package it looks like the cache never gets pruned in normal operation unless you set the max_age option when instantiating the cache and then try to access a cache key that is older than that age. Currently the caching compiler package doesn't set a max age, and even if it did, it sets the key to a hash of the compilation result and therefore it would only prune if you hadn't made changes to your sass files and the last time it was compiled was longer than the `max_age.

I think that the solution might lie in a PR on meteor core repo to add a max_age option and manually calling cache.prune() on the cache if it grows beyond a certain number of objects.

[derwaldgeist]

Thanks for looking into this, highly appreciated!