Hello, I need help to track down this issue because I don’t feel familiar with how caching-compiler works.
I use nathantreid:static-assets and I noticed that .meteor/local/plugin-cache/nathantreid_static-assets/ contains a number of copies of the same files:
$ sha256sum * | sort
0103a57f1e465254e898a0bf6d2159f7fb39edcb93beeb948b066c09fdb6cd6e 199337a34f1da81b7a5e79bb997e188980da9dc9.cache.tmp.24wRzCnybon4aH6kB
0103a57f1e465254e898a0bf6d2159f7fb39edcb93beeb948b066c09fdb6cd6e 199337a34f1da81b7a5e79bb997e188980da9dc9.cache.tmp.7YJe97FH3C6KerPC9
0103a57f1e465254e898a0bf6d2159f7fb39edcb93beeb948b066c09fdb6cd6e 199337a34f1da81b7a5e79bb997e188980da9dc9.cache.tmp.ba7GeHiFaorMYat8v
0103a57f1e465254e898a0bf6d2159f7fb39edcb93beeb948b066c09fdb6cd6e 199337a34f1da81b7a5e79bb997e188980da9dc9.cache.tmp.d44wgGeCxzCdohgEb
0103a57f1e465254e898a0bf6d2159f7fb39edcb93beeb948b066c09fdb6cd6e 199337a34f1da81b7a5e79bb997e188980da9dc9.cache.tmp.tmAfokLvMAcHLKk9u
018dbf2faca5331903d3587c437697b55cadb0678c3c44f731229f93b04ed7e0 26e4a948a78b8ac56ae0bddba7ea0c4b348954c0.cache.tmp.45fLfTw3fRJSt6RPD
018dbf2faca5331903d3587c437697b55cadb0678c3c44f731229f93b04ed7e0 26e4a948a78b8ac56ae0bddba7ea0c4b348954c0.cache.tmp.6oryGnLaxk5gNB5c6
018dbf2faca5331903d3587c437697b55cadb0678c3c44f731229f93b04ed7e0 26e4a948a78b8ac56ae0bddba7ea0c4b348954c0.cache.tmp.Hvm97shZAdEWFt2Fv
018dbf2faca5331903d3587c437697b55cadb0678c3c44f731229f93b04ed7e0 26e4a948a78b8ac56ae0bddba7ea0c4b348954c0.cache.tmp.YNjrMwWZuf9qE7BYN
First I suspected a bug in nathantreid:static-assets (hi Nathan! Pity that you have to give up Meteor!) but as I read the source code, it became clear that it inherits from the caching-compiler cache and seems to do everything right regarding setting cache keys as one-way hash functions of files etc.
The trouble is that every time I change anything in my project, the .meteor/local/plugin-cache/nathantreid_static-assets/ directory grows by several hundreds of megabytes… How do I investigate this problem? I am using Meteor 1.8.2 (just upgraded from a release candidate and confirmed that the bug is still there).