[wasm] Catch error from loading "node:crypto" module (dotnet#78916)

* Catch error from loading node:crypto module. * Throw error with explanation when crypto module is not available. * Fix providing error throwing polyfill.
maraf · Dec 7, 2022 · 0ec98b0 · 0ec98b0
1 parent 4ebb4a9
commit 0ec98b0
Showing 1 changed file with 12 additions and 2 deletions.
diff --git a/src/mono/wasm/runtime/polyfills.ts b/src/mono/wasm/runtime/polyfills.ts
@@ -201,8 +201,18 @@ export async function init_polyfills_async(): Promise<void> {
             globalThis.crypto = <any>{};
         }
         if (!globalThis.crypto.getRandomValues) {
-            const nodeCrypto = INTERNAL.require("node:crypto");
-            if (nodeCrypto.webcrypto) {
+            let nodeCrypto: any = undefined;
+            try {
+                nodeCrypto = INTERNAL.require("node:crypto");
+            } catch (err: any) {
+                // Noop, error throwing polyfill provided bellow
+            }
+
+            if (!nodeCrypto) {
+                globalThis.crypto.getRandomValues = () => { 
+                    throw new Error("Using node without crypto support. To enable current operation, either provide polyfill for 'globalThis.crypto.getRandomValues' or enable 'node:crypto' module."); 
+                };
+            } else if (nodeCrypto.webcrypto) {
                 globalThis.crypto = nodeCrypto.webcrypto;
             } else if (nodeCrypto.randomBytes) {
                 globalThis.crypto.getRandomValues = (buffer: TypedArray) => {