You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I think it would be cool if we can provide to config.js a cache policy function that can be
provided by users of npm_lazy.
What I am thinking is of something like having the ability to add a "require" line at the top of config.js that will point to a file which will be able to contain a cache policy function.
Then server.js will use this cache policy function for caching.
For example, we can use this in order to define "whitelist" or "blacklist" (for example, names of modules that will be always fetched from the public npm repo , no matter what).
We should also consider may having some cahce loader function that will be able to store the cache on some other secondary storage.
I will be more than glad to assist and provide some code, if you're interested.
Cheers,
Yair
The text was updated successfully, but these errors were encountered:
Hi,
I think it would be cool if we can provide to config.js a cache policy function that can be
provided by users of npm_lazy.
What I am thinking is of something like having the ability to add a "require" line at the top of config.js that will point to a file which will be able to contain a cache policy function.
Then server.js will use this cache policy function for caching.
For example, we can use this in order to define "whitelist" or "blacklist" (for example, names of modules that will be always fetched from the public npm repo , no matter what).
We should also consider may having some cahce loader function that will be able to store the cache on some other secondary storage.
I will be more than glad to assist and provide some code, if you're interested.
Cheers,
Yair
The text was updated successfully, but these errors were encountered: