Add cache invalidation or cache setting API #32

Activity

1. cspotcode

   changed the title [-]Add cache invalidation API[/-] [+]Add cache invalidation or cache setting API[/+] on Oct 17, 2021
2. cspotcode commented on Oct 17, 2021

   

   cspotcode

   on Oct 17, 2021

   Last edited by cspotcode

   OwnerAuthor

   More actions

   Thought about this some more. Might make sense to expose an API for setting cache entries. Every time we need to invalidate a cache entry, it is because we have a new value for it. Maybe just set that new value into the cache.

   This mimics the functionality of hookRequire without necessitating a hook.

   On the other hand, hookRequire saves fs calls by storing every loaded module into the cache.
3. cspotcode commented on Oct 17, 2021

   

   cspotcode

   on Oct 17, 2021

   OwnerAuthor

   More actions

   If a consumer uses emptyCacheBetweenOperations then they should still take care to implement retrieveSourceMap. Even then, new SourceMapConsumer() is called every time, and I'm not sure of the performance implications.

   This is why I'm averse to emptyCacheBetweenOperations.