For some reason, my .meteor/local/bundler-cache/linker folder is 700+MB of .cache files. These files seem to continually grow over time. If I meteor reset and start over, my project goes from 100MB to 300MB immediately when I run meteor the first time.
Any thoughts on how figure out what is going wrong? How can I find out what is writing to bundler_cache folder? Does anyone know normal behavior for those files?
webapp|master ⇒ du -sh .meteor/local/bundler-cache/linker
709M .meteor/local/bundler-cache/linker
linker|master ⇒ du 4e66b88173386163ea6cd7a6ee945a12f3ab5920.cache
208 4e66b88173386163ea6cd7a6ee945a12f3ab5920.cache
bundler-cache|master ⇒ find linker -type f | wc -l
619
Only ~700 MB’s? Consider yourself lucky - I’m usually around 1.5 gigs. There isn’t anything wrong here however, this is normal Meteor behaviour. Meteor uses a build system called Isobuild, which ultimately uses the bundler-cache directory for its cache files. If you want the nitty gritty details about what’s writing to it and why, take a look at https://github.com/meteor/meteor/blob/devel/tools/isobuild/bundler.js.
I was hoping I finally figured out why my Meteor project was so slow when
developing locally. Takes 12-15 seconds for Meteor to reload.
It’s a fairly large project, but still shouldn’t take that long right. Any
thoughts on where to look? It really slows down dev time (I have a '14 air
4gb mem 128gb hd with plenty of open space).
I realize that thats not enough info for anything definitive, but would
appreciate any points in the right direction.
Wow, that seems a bit excessive. I’m sure it’s okay, but you might want to clear things out. I guess the only reason to be worried would be if you’re always low on disk space like I am (I just keep deleting family photos to make room for cache files … goes over really well with my wife …).