Pregenerating database introspection output?
Evaluating massive-js for a "serverless" application (zeit now lambdas)
Is it possible to perform the database introspection ahead of time and not during connection initialization at runtime.
Would it make sense to save the output of the database introspection as a .js file and just load it at runtime to initialize massive?