fix: resolving module load in linux (#250)

HomecareHomebase · Apr 5, 2022 · 5b90aa1 · 5b90aa1
1 parent 3e3d6b6
commit 5b90aa1
Show file tree

Hide file tree

Showing 11 changed files with 29,133 additions and 22,166 deletions.
diff --git a/core/src/ingredient-manager.ts b/core/src/ingredient-manager.ts
@@ -4,6 +4,9 @@ import {DeploymentContext} from "./deployment-context"
 import * as process from "process"
 import * as fs from 'fs'
 
+const {createRequire} = require('module');
+const path = require('path');
+
 export class IngredientManager {
 
     private static ingredientTypes : Map<string, IIngredientType>
@@ -13,9 +16,15 @@ export class IngredientManager {
     private static ingredientTypesVersions : Map<string, string>
         = new Map<string, string>()
 
+    public static RequireIngredient(moduleName: string): any {
+        const packagePath = path.resolve('./', 'noop.js');
+        const module = createRequire(packagePath)(moduleName);
+        return module;
+    }
+
     public static Register(moduleName: string):void {
 
-        var module = require(moduleName)
+        const module = IngredientManager.RequireIngredient(moduleName);
 
         if (module.plugin){
 

diff --git a/ingredient/ingredient-functions/package-lock.json b/ingredient/ingredient-functions/package-lock.json
diff --git a/ingredient/ingredient-network-interface/package-lock.json b/ingredient/ingredient-network-interface/package-lock.json
diff --git a/ingredient/ingredient-sql-dwh/package-lock.json b/ingredient/ingredient-sql-dwh/package-lock.json