The initial support for ESM entrypoint in SEA didn't support code cache. This patch implements that by following a path similar to how code cache in CJS SEA entrypoint is supported: at build time we generate the code cache from C++ and put it into the sea blob, and at runtime we consume it via a special case in compilation routines - for CJS this was CompileFunctionForCJSLoader, in the case of SourceTextModule, it's in Module::New. PR-URL: https://github.com/nodejs/node/pull/62158 Refs: https://github.com/nodejs/node/pull/61813 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> |
||
|---|---|---|
| .. | ||
| addon | ||
| already-exists | ||
| asset-keys | ||
| asset-keys-empty | ||
| assets | ||
| assets-invalid-type | ||
| assets-nonexistent-file | ||
| assets-raw | ||
| basic | ||
| disable-experimental-warning | ||
| empty | ||
| esm | ||
| esm-code-cache | ||
| exec-argv | ||
| exec-argv-empty | ||
| exec-argv-extension-cli | ||
| exec-argv-extension-env | ||
| exec-argv-extension-none | ||
| executable-field | ||
| inspect | ||
| inspect-in-sea-flags | ||
| simple | ||
| snapshot | ||
| snapshot-and-code-cache | ||
| snapshot-worker | ||
| use-code-cache | ||