From cd6e6af174b7324e584762bfd55930a93808b70e Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Wed, 27 Sep 2023 11:34:18 +0200 Subject: [PATCH] fix(build): disable startup snapshot support again for now MONGOSH-1605 (#1687) See the comments in MONGOSH-1604/MONGOSH-1605. A proper solution involves at least updates to Node.js core, so just disabling it again should be a good workaround for now. --- packages/build/src/compile/signable-compiler.ts | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/packages/build/src/compile/signable-compiler.ts b/packages/build/src/compile/signable-compiler.ts index a67b13cb3..c1e81f619 100644 --- a/packages/build/src/compile/signable-compiler.ts +++ b/packages/build/src/compile/signable-compiler.ts @@ -176,9 +176,11 @@ export class SignableCompiler { preCompileHook, executableMetadata: this.executableMetadata, // Node.js startup snapshots are an experimental feature of Node.js. - // If, at some point, something breaks because of it, we can always - // go back to using `useCodeCache: true` only. - useNodeSnapshot: true, + // TODO(MONGOSH-1605): Re-enable startup snapshots after figuring out + // issues with running the binary when CPU features differ + // significantly. + useCodeCache: true, + // useNodeSnapshot: true, }); } }