Module cache hooks

[Lakedaemon]

What is the problem this feature will solve?

My project builds immutable modules and persistently stores them in a lmdb instance

I would like to be able to :

• cache these modules in my lmdb instance after compilation
• provide those modules from my lmdb instance to the node cache, bypassing compilation

This cannot be done through the load hooks (because load output needs to be compiled, it cannot be a module)
And the module cache api doesn't have hooks for customization

In my project, those lmdb modules are built ONCE (sometimes modified/versioned) and used for years to build a lot of other stuff.
My project aims to provide free education. Those modules are animations/courses/knowledge

What is the feature you are proposing to solve the problem?

2 hooks would be nice :
1 hook so that a callBack is called with the module, just after compilation.
1 hook to that a callBack with the module data (url, ...) with shortcut can provide a module when the cache is hit for the first time

with some api to invalidate the cache (custom and node) on changes
(a onChange callBack ?)

What alternatives have you considered?

I can make it work TODAY without this by injecting code in my modules but this smells.

nodes is a lot about building modules, giving more control to the user will bring new features/good stuff

With this, it would be WAY cleaner

[Lakedaemon]

Another way to implement it would be to allow the user to provide his own cache structure (instead of hardcoding it in nodes and going through hoops/hooks to customize it to please the user

Please notice that in my use case,
only SOME particular modules (the courses & their building blocks) are persistently stored
a lot of regular js modules are just handled the regular/standard way (re computed/cached by nodes)