Make sure paths code is run in NodeJS context

ChainSafe · Nov 19, 2020 · 7a61d2d · 7a61d2d
1 parent 3f98022
commit 7a61d2d
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/src/scripts/paths.ts b/src/scripts/paths.ts
@@ -20,6 +20,11 @@ export function getBinaryName() {
   const platform = process.platform;
   const arch = process.arch;
   const nodeV8CppApiVersion = process.versions.modules;
+  if (!process) throw new NotNodeJsError("global object");
+  if (!platform) throw new NotNodeJsError("process.platform");
+  if (!arch) throw new NotNodeJsError("process.arch");
+  if (!process.versions.modules)
+    throw new NotNodeJsError("process.versions.modules");
 
   return [platform, arch, nodeV8CppApiVersion, "binding.node"].join("-");
 }
@@ -40,3 +45,11 @@ export function ensureDirFromFilepath(filepath: string) {
     fs.mkdirSync(dirpath, { recursive: true });
   }
 }
+
+export class NotNodeJsError extends Error {
+  constructor(missingItem: string) {
+    super(
+      `BLST bindings loader should only run in a NodeJS context: ${missingItem}`
+    );
+  }
+}