hard-source-webpack-plugin icon indicating copy to clipboard operation
hard-source-webpack-plugin copied to clipboard

Published 20 hours ago • verified publisher icon mzgoddard

Find out what invalidates the cache

Open stereokai opened this issue 7 years ago • 5 comments

@mzgoddard I love HardSource and appreciate the amazing work and ample thought put into it. After having been using for a while, I feel like HardSource more often then not invalidates the cache when it shouldn't. How do I go about finding out what exactly caused HardSource to detect a "false negative" and invalidate the cache? Perhaps I can contribute back improvements to HardSource. Thanks!

stereokai avatar Mar 20 '18 16:03 stereokai

@mzgoddard bump! :)

stereokai avatar May 22 '18 09:05 stereokai

@stereokai :wink: hard-source-webpack-plugin@next is working towards this and messaging about the cache size and automatic clean up of old caches. Right now that consists of stating a summary of files that goes into the environment hash and referencing the cache related to each hard-source message.

Probably during a patch for 0.7 or working in 0.8's alpha I think I'm going to add storing the hashed info and rendering a diff after the hash changes.

mzgoddard avatar May 22 '18 20:05 mzgoddard

People always say I'm ahead of my time 😁 Well that's awesome news on it's own!

Is there anything I can do now (by debugging maybe) to figure that out on my own without bothering you too much?

stereokai avatar May 23 '18 08:05 stereokai

@mzgoddard Hey buddy, any chance we can allocate some time for this? Cheers :)

stereokai avatar Dec 19 '18 11:12 stereokai

@mzgoddard trying to bring this back into the spotlight :)

stereokai avatar Feb 27 '19 13:02 stereokai