Generating Compile Cache Ahead of Runtime

What is the problem this feature will solve?

It is currently not possible to generate the compile cache without executing the files that will be cached.

Currently, container images and lambda functions can't easily generate code caches ahead of the actual runtime, since the code may have effects you may not want to execute early.

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

Would it be possible to add a way to generate the compile cache without executing the relevant files, i.e. walking the module tree from the entry point, generating caches along the way?

Perhaps something like node --generate-compile-cache path/to/entrypoint.mjs
and/or

module.generateCompileCache("path/to/entrypoint.mjs")

What alternatives have you considered?

You may be able to work around this by adding "dry-run" code paths specifically for code cache generation, but this is a hacky workaround that can require massive effort.

首先检查 Node.js 现有的编译缓存行为，以及提议的入口点 --generate-compile-cache 和 module.generateCompileCache()。确定如何在不执行应用程序代码的情况下遍历入口点的模块树。完成的标准是有一种经过文档说明和测试的方法，能够在运行时之前生成相关的编译缓存。